From: bjorn rohde jensen <bjensen@fastmail.fm>
To: Ricardo Anguiano <anguiano@codesourcery.com>
Cc: Jeff Holle <jeff.holle@verizon.net>, gcc-help@gcc.gnu.org
Subject: Re: Problems with gcc 3.2
Date: Wed, 23 Oct 2002 10:30:00 -0000 [thread overview]
Message-ID: <3DB6DCC9.90802@fastmail.fm> (raw)
In-Reply-To: <m3bs5loz21.fsf@mordack.codesourcery.com>
Hi guys,
How sure are you about the reliability of the
>ImportError: libstdc++.so.5: cannot open shared object file: No such
>file or directory
error message?
Could this be a problem relating to the C++ ABI changes from gcc 2
to gcc 3? C++ libraries created with one probably wont work properly
or even link with a program compiled with the other. It sounds like,
python likes dynamic loading of libraries, and i doubt, the runtime
linker will be any more successful than the compile time linker.
Just a thought;)
Yours sincererly,
Bjorn
next prev parent reply other threads:[~2002-10-23 17:30 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
2002-10-23 10:30 ` bjorn rohde jensen [this message]
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=3DB6DCC9.90802@fastmail.fm \
--to=bjensen@fastmail.fm \
--cc=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).