the new build system in binutils sets up custom LD_LIBRARY_PATHs which can cause
conflicts between the build and host. if you take binutils-2.17.50.0.17 and
build/install it with --enable-shared, your host binutils will all be linked
against libbfd-2.17.50.0.17.20070615.so:
$ readelf -d `which as` | grep NEEDED.*2.17
0x0000000000000001 (NEEDED) Shared library:
[libopcodes-2.17.50.0.17.20070615.so]
0x0000000000000001 (NEEDED) Shared library:
[libbfd-2.17.50.0.17.20070615.so]
but if you turn and and try to build it again, the LD_LIBRARY_PATH will be set
to your local build directories:
LD_LIBRARY_PATH=.../build/bfd/.libs:.../build/opcodes/.libs:....
and this makes your installed `as` very angry, especially when cross-compiling
as the local libraries are not targetting the same thing as your host libraries.
i cant think of any use for these LD_LIBRARY_PATHs as each binutils utility
includes a little libtool wrapper script which allows you to execute them in the
build dir and make sure the local shared libs are found and used properly ... so
`make check` would work OK ...
--
Summary: new library handling in binutils causes trouble with --
enable-shared
Product: binutils
Version: 2.18
Status: NEW
Severity: normal
Priority: P2
Component: binutils
AssignedTo: unassigned at sources dot redhat dot com
ReportedBy: vapier at gentoo dot org
CC: bug-binutils at gnu dot org
http://sourceware.org/bugzilla/show_bug.cgi?id=4970
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
_______________________________________________
bug-binutils mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-binutils
