Re: c++/10268: C++ executables fail: libstdc++.so.5 not found

[Hallvard B Furuseth <h.b.furuseth@usit.uio.no>]

The following reply was made to PR c++/10268; it has been noted by GNATS.

From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
To: Christian Ehrhardt <ehrhardt@mathematik.uni-ulm.de>
Cc: gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: c++/10268: C++ executables fail: libstdc++.so.5 not found
Date: Mon, 31 Mar 2003 16:57:50 +0200

 [I've excluded gcc-prs@gcc.gnu.org from the cc: list, since it rejects
 mail from "outsiders".]
 
 Christian Ehrhardt writes:
 > This is even covered by the gcc FAQ at http://gcc.gnu.org/faq.html#rpath
 
 Oops.
 
 >> If you don't want to add to the executable's path, I think you should
 >> only build static libraries.  If one configures gcc to build dynamic
 >> libraries, add the path and warn about whatever the problem is with
 >> adding such a path, or don't add it and give a very loud warning that
 >> g++ will build executables that don't work.
 > 
 > There is a loud warning when you install the shared libraries!
 
 Oh.  I found it in the typescript now, I think it scrolled away during
 installation.  Though I still think a warning at the end of configure
 would be better (so it wouldn't scroll away).  I think I've seen the
 warning before though.  I guess it just didn't occur to me that it
 applied even if I didn't use the -L option myself.
 
 Thanks.
 
 -- 
 Hallvard