From: Ricardo Anguiano <anguiano@codesourcery.com>
To: Jeff Holle <jeff.holle@verizon.net>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Problems with gcc 3.2
Date: Wed, 23 Oct 2002 10:17:00 -0000 [thread overview]
Message-ID: <m3bs5loz21.fsf@mordack.codesourcery.com> (raw)
In-Reply-To: <3DB772E2.2040602@verizon.net>
Jeff Holle <jeff.holle@verizon.net> writes:
> I've just installed gcc 3.2 on my linux system (Mandrake 8.2).
> Typing "gcc -v" from command line reports:
>
> Configured with: ./configure
> Thread model: posix
> gcc version 3.2
>
> In compiling and running a simple boost.python extension module (which
> worked with gcc 2.96.0), I get:
>
> $python hello.py
> Traceback (most recent call last):
> File "hello.py", line 1, in ?
> import HELLO
> ImportError: libstdc++.so.5: cannot open shared object file: No such
> file or directory
>
> This appears to be because libstdc++.so.5 is installed in
> /usr/local/lib instead of /usr/lib (where the 2.96.0 shared libraries
> seem to be).
>
> What do I have to do to my environment to fix this?
>
> Note:
> I tried to define LD_LIBRARY_PATH (which was not previously defined)
> to "/usr/local/lib:/usr/lib:/lib", to no affect.
That's the right environment variable, but I don't know why it isn't
working. You can try either:
0) printing the value of LD_LIBRARY_PATH from within the
python script to make sure it is defined and has the right
value.
1) compiling the module statically (-static).
2) copying libstdc++.so.5 into /usr/lib
HTH,
--
Ricardo Anguiano
CodeSourcery, LLC
next prev parent reply other threads:[~2002-10-23 17:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-22 21:16 Jeff Holle
2002-10-23 3:31 ` Claudio Bley
2002-10-23 10:17 ` Ricardo Anguiano [this message]
2002-10-23 10:30 ` bjorn rohde jensen
2002-10-23 11:33 ` Ricardo Anguiano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3bs5loz21.fsf@mordack.codesourcery.com \
--to=anguiano@codesourcery.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jeff.holle@verizon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).