This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
exes can't find libstdc++.so without help
- To: GCC Bugs Mailing List <gcc-bugs at gcc dot gnu dot org>
- Subject: exes can't find libstdc++.so without help
- From: Neil Bird <neil dot bird at uk dot thalesgroup dot com>
- Date: Thu, 05 Jul 2001 08:43:09 +0100
- Organization: Thales Sensors (but only on behalf of myself)
- Reply-To: GCC Bugs Mailing List <gcc-bugs at gcc dot gnu dot org>
I've done a test compile of gcc3, and, apart from a little
hoop jumping wrt. a bizarre ltconfig bug, it seemed to go
smoothly.
However, c++ progs. that it compiles use libstdc++.so (as
that's the default, and what I want for the most part), but they
don't seemingly have any knowledge of where to find it:
ld.so.1: a.out: fatal: libstdc++.so.3: open failed: No such file
or directory
Are all users of g++ now expected to have to set
LD_LIBRARY_PATH up to include the obscure
/path/to/gcc/lib/gcc-lib/sparc-sun-solaris2.6/3.0 - or whatever
happens to be correct for them?
I really find it difficult to believe that, having used a
specific libstdc++.so, the exe. has no -R or -R-like option to
explain where it needs it's most fundamental library.
It's not as if I can even copy the .so into a 'standard'
place, as it's an OS/gcc-version specific library.
Has something gone wrong, or this this actually the case??
For the time being, I've added a -R to the '*link:' spec file
entry.
--
=================- http://www.thalesgroup.com/ -================
Neil Bird Principal Engineer |
work - mailto:neil.bird@uk.thalesgroup.com | $> cd /pub
personal - mailto:neil@fnxweb.com | $> more beer