This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: Problematic linking between glibc and shared libgcc
- To: Alexandre Oliva <aoliva at redhat dot com>
- Subject: Re: Problematic linking between glibc and shared libgcc
- From: David Edelsohn <dje at watson dot ibm dot com>
- Date: Wed, 21 Feb 2001 09:41:35 -0500
- cc: Mark Mitchell <mark at codesourcery dot com>, rra at stanford dot edu, gcc at gcc dot gnu dot org, libc-alpha at sources dot redhat dot com
>>>>> Alexandre Oliva writes:
Alexandre> This is not true. If you do move stuff, you may have to set
Alexandre> LD_LIBRARY_PATH so that the moved libraries are still found, but
Alexandre> that's all. I.e., it's no worse than having to set LD_LIBRARY_PATH
Alexandre> always, and, in the general case, it's better, because you don't have
Alexandre> to set LD_LIBRARY_PATH at all.
I disagree with this slightly. There is the obscure case where
the -rpath value points to a filesystem which no longer exists or has
mounting problems. In that example, the invalid -rpath value can cause
severe performance problems and essentially hang all applications
depending on the shared library until a timeout occurs.
David