[Bug bootstrap/40572] gcc insistance on using LD_LIBRARY_PATH and ignoring LD_FLAGS

[david dot kirkby at onetel dot net]

------- Comment #7 from david dot kirkby at onetel dot net  2009-06-27 22:31 -------
(In reply to comment #6)
> LD_LIBRARY_PATH is for the runtime linker/loader so it is needed as you are
> running programs which use shared libraries stored in a "non standard" place.
> 

So is any user who uses the compiler going to need to set  LD_LIBRARY_PATH ?
That would seem crazy if that is true. I don't need to set LD_LIBRARY_PATH on
my Sun to use the gcc from Blastwave, which resides in /opt/csw/bin/gcc or the
one which Sun ship which resides in /usr/sfw/bin. 

It is impossible for me to create a gcc-4.4.0 which links to libraries in
locations I chose, without users having to set LD_LIBRARY_PATH? It is not
possible to specify the locations of the libraries? I thought options like:

--with-mpfr-lib=PATH    specify directory for the installed MPFR library

were supposed to override the default /usr/local/lib. 

In some ways, an option like --ignore-usr-local would be nice on LOTS of
programs. The trouble with the 'standard' /usr/local is that it tends to
accumulate a lot of rubbish. 


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40572