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: bjorn rohde jensen <bjensen at fastmail dot fm>
- To: Ricardo Anguiano <anguiano at codesourcery dot com>
- Cc: Jeff Holle <jeff dot holle at verizon dot net>, gcc-help at gcc dot gnu dot org
- Date: Wed, 23 Oct 2002 19:30:49 +0200
- Subject: Re: Problems with gcc 3.2
- References: <3DB772E2.2040602@verizon.net> <m3bs5loz21.fsf@mordack.codesourcery.com>
- Reply-to: bjensen at fastmail dot fm
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