linker SEARCH_DIR order

[George.R.Goffe@seagate.com]

Alan,

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.

George...






Alan Modra <amodra@bigpond.net.au>@sources.redhat.com on 04/24/2002
05:38:07 AM

Sent by:  binutils-owner@sources.redhat.com


To:   binutils@sources.redhat.com
cc:

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?

--
Alan Modra
IBM OzLabs - Linux Technology Centre