This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Problems with gcc 3.2
- From: "Claudio Bley" <bley at cs dot uni-magdeburg dot de>
- To: Jeff Holle <jeff dot holle at verizon dot net>
- Cc: gcc-help at gcc dot gnu dot org
- Date: Wed, 23 Oct 2002 12:32:07 +0200
- Subject: Re: Problems with gcc 3.2
- References: <3DB772E2.2040602@verizon.net>
>>>>> "Jeff" == Jeff Holle <jeff.holle@verizon.net> writes:
Jeff> $python hello.py Traceback (most recent call last):
Jeff> File "hello.py", line 1, in ? import HELLO ImportError:
Jeff> libstdc++.so.5: cannot open shared object file: No such file
Jeff> or directory
Jeff> This appears to be because libstdc++.so.5 is installed in
Jeff> /usr/local/lib instead of /usr/lib (where the 2.96.0 shared
Jeff> libraries seem to be).
Jeff> What do I have to do to my environment to fix this?
Jeff> Note: I tried to define LD_LIBRARY_PATH (which was not
Jeff> previously defined) to "/usr/local/lib:/usr/lib:/lib", to no
Jeff> affect.
Did you export that variable? It should work then. (and you don't need
to specify paths already searched for, just /usr/local/lib)
On the other hand you might just add /usr/local/lib to /etc/ld.so.conf
and run ldconfig. Afterwards running ldd on HELLO.so all library
references should be resolved.
--
Claudio Bley ASCII ribbon campaign (")
Debian GNU/Linux advocate - against HTML email X
http://www.cs.uni-magdeburg.de/~bley/ & vCards / \