On Wed, 13 Sep 2006, Ralf Wildenhues wrote:
Also my gcc likes to output stuff like
......
/usr/lib/gcc/x86_64-linux-gnu/4.0.3
/usr/lib/gcc/x86_64-linux-gnu/4.0.3
/usr/lib/gcc/x86_64-linux-gnu/4.0.3/../../../../lib64
/usr/lib/gcc/x86_64-linux-gnu/4.0.3/../../..
/lib/../lib64
/usr/lib/../lib64
without a flag (i.e., -m64). Looks kinda scary to not have /usr/lib and
/usr/lib32 and /usr/lib64 in this list.
It's nice to know that gcc-4.0.3 has fixed one part of the problem. However,
not having /usr/lib, /lib, and /usr/local/lib is really bad. The above
output should be compared with the default (GNU) linker search path as,
e.g., in /usr/x86_64-linux-gnu/lib/ldsripts/elf_x86_64.x:
SEARCH_DIR("/usr/x86_64-linux-gnu/lib64");
SEARCH_DIR("/usr/local/lib64");
SEARCH_DIR("/lib64");
SEARCH_DIR("/usr/lib64");
SEARCH_DIR("/usr/x86_64-linux-gnu/lib");
SEARCH_DIR("/usr/local/lib");
SEARCH_DIR("/lib");
SEARCH_DIR("/usr/lib");
containing both .../lib64 and .../lib directories.
regards
Peter Breitenlohner <[EMAIL PROTECTED]>
_______________________________________________
Bug-libtool mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-libtool
