This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: incorrect library path in 3.0.1?
- To: Nick Papadonis <npapadon at yahoo dot com>
- Subject: Re: incorrect library path in 3.0.1?
- From: Alexandre Oliva <aoliva at redhat dot com>
- Date: 29 Sep 2001 05:21:10 -0300
- Cc: e_macdon at hotmail dot com, andy at fag dot ucd dot ie, gcc-bugs at gcc dot gnu dot org
- Organization: GCC Team, Red Hat
- References: <m366amkhq7.fsf@yahoo.com>
On Sep 13, 2001, Nick Papadonis <npapadon@yahoo.com> wrote:
> I believe it is from the GCC 3.0 compilation. I set the install prefix
> for /usr/local/lib, however this is not reflected in the compiled gcc
> executable.
It is. It looks for libraries, at build time, in the configured
prefix (actually, it can also cope with having the install tree
moved). But it won't encode the library search paths into
executables, because there are a number of people who believe this is
not the right thing to do, because it prevents someone from using
LD_LIBRARY_PATH to override the use of those libraries with those in
another directory when the libraries are present in the encoded
directory. I find this argument quite reasonable, but I personally
consider the inconvenience of forcing every user to set
LD_LIBRARY_PATH or every application builder to set LD_RUN_PATH a bit
too much, so I'd rather give users the option to choose whether to
encode the dynamic paths into executables or not. Unfortunately, this
is quite hard to do correctly and portably, so it hasn't been done
yet.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me