This is the mail archive of the
mailing list for the binutils project.
Re: linker SEARCH_DIR order
- From: George dot R dot Goffe at seagate dot com
- To: amodra at bigpond dot net dot au
- Cc: binutils at sources dot redhat dot com
- Date: Wed, 24 Apr 2002 05:51:05 -0700
- Subject: Re: linker SEARCH_DIR order
I've been trying to get someone (anyone) interested in having the configure
process look to --prefix= as a HINT as to where to look first to find the
various "things" that it needs to do it's thing.
For example, I have /usr/ccs/bin/ld|as, /usr/local/bin/ld|as and a
/usr/lsd/SunOS.5.8/bin/ld|as and want configure to use the later versions.
configure still insists on looking at /usr/ccs/bin which breaks the builds.
Good luck finding someone interested.
Alan Modra <firstname.lastname@example.org>@sources.redhat.com on 04/24/2002
Sent by: email@example.com
Subject: linker SEARCH_DIR order
Why is the default native linker search path in this order?
/lib /usr/lib /usr/local/lib $prefix/$target/lib
Wouldn't it be more sense to be reversed, or to match gcc,
$prefix/$target/lib /usr/local/lib /lib /usr/lib ?
The idea being that $prefix/$target/lib has anything that's
particularly target dependent, and /usr/local is the place
where new tools and libs are installed, so should override
/lib and /usr/lib. Comments?
IBM OzLabs - Linux Technology Centre