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: libio regressions, shared libs.



  In message <3778E626.650A122E@interix.com>you write:
  > Jeff: I suspect you missed a critical point in my original message:
  > the tool path tools are built with the NEW shared library, which
  > is versioned.
Why is this important.

   > Thus, if LD_LIBRARY_PATH is not set to include
  > a directory containing the new shared library, ld.so will not
  > find it at all.
But the dejagnu code should be setting LD_LIBRRAY_PATH to point to the
directory which contains the newly built library.  It already does this.

  > (That is, since libc.so.2.2-19990628 is not
  > in any of the usual places, LD_LIBRARY_PATH must be set or
  > gcc will not run, since gcc depencs on libc.so.2.2-19990628.)
This is what wasn't explained well.  You're talking about gcc itself?!?
You need to explain this better since I don't see how gcc itself is
getting linked against a C library in a nonstandard location.

jeff


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