This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Dynamic linker is unable to find GCC libraries



Benoit Hudson <bhudson@ptolemy.arc.nasa.gov> writes:

> On Thu, Jul 06, 2000 at 12:23:33AM -0300, Alexandre Oliva wrote:
> > See?  It's discarding the shared library.  But collect2 needs to find
> > the library, and it depends on being able to find it, that's why you
> > need LD_LIBRARY_PATH.
> 
> Great!  An old version discards the library.  For some reason, a newer
> version decides it can't discard (I'm using the same ld).  Why should me,
> the user, care?

It means you should use the new linker.  The old behaviour is buggy.

> collect2 clearly is able to find its library without an LD_LIBRARY_PATH.
> It's trivial to do: just hard-code the path into gcc when we compile gcc.
> We need to do this for crt1.0 and so on anyway; why not put libstdc++ there
> too?  (and in fact, it is there, for 2.95.2).

For one thing, gcc can be moved by the user.  So any solution that
involves hard-coding paths (in gcc or in executables) is bad.

-- 
- Geoffrey Keating <geoffk@cygnus.com>

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]