This post is relative to the Sysroot - Version
SVN-0.0.1-20061211-x86 guide.
This may already be known, but libtools appears to be problematic in two areas
of this
build method. I say 'appears' because I am by no means an expert on either
autotools,
or specifically libtools.
The first issue, is that during installation of the installation the host
supplied libtools creates *.la
files with dependency libs in both the /mnt/cfls/cross-tools and
/mnt/clfrs/sources directories.
This can be demonstrated by performing an installation, and then searching for
all *.la files, then
grepping them for 'clfs'.
# find /* -name *.la -exec grep clfs '{}' \;
These are the .la files generated during the installation (excluding those
created in .../cross-tools):
/usr/lib/libgettextpo.la
/usr/lib/libasprintf.la
/usr/lib/libpam_misc.la
/usr/lib/libpam.la
/usr/lib/libssp_nonshared.la
/usr/lib/libsupc++.la
/usr/lib/libbfd.la
/usr/lib/libshadow.la
/usr/lib/libmudflap.la
/usr/lib/libmudflapth.la
/usr/lib/libmagic.la
/usr/lib/libgettextlib.la
/usr/lib/libgettextsrc.la
/usr/lib/libssp.la
/usr/lib/libpamc.la
/usr/lib/libltdl.la
/usr/lib/libstdc++.la
/usr/lib/libopcodes.la
Of those, these are the ones with problematic references to what will become
non-
existent paths after installation:
/usr/lib/libasprintf.la
/usr/lib/libsupc++.la
/usr/lib/libbfd.la
/usr/lib/libstdc++.la
Libtools may be creating other library problems, but they are not apparent to
me at this time.
The second issue observed, is that the libtool installed to the target system,
seems to be configured to
use the cross-tools built gcc and binutils. The following variables begin with
the target triplet (when only
the application name is expected):
AR
LTCC
CC
LD
NM
STRIP
AS
RANLIB
old_striplib
striplib
Also of note is that although the compile time system search paths for
libraries references now non-
existent paths (/mnt/clfs/cross-tools and /mnt/clfs), the run-time system
search path for libraries does
not.
I bumped into this when libusb failed to install (after the base install), and
have been searching for
corrective action since. I found two promising sources of information, but
they are unfortunately based
on an earlier version of libtools using ltconfig. As you probably know, the
latest stable libtool version
uses configure and not ltconfig.
Best regards,
Harvey
____________________________________________________________________________________
Any questions? Get answers on any topic at www.Answers.yahoo.com. Try it now.
_______________________________________________
Clfs-dev mailing list
[email protected]
http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-dev
