Problems with gcc 3.2

Ricardo Anguiano anguiano@codesourcery.com
Wed Oct 23 11:33:00 GMT 2002


bjorn rohde jensen <bjensen@fastmail.fm> writes:
>   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;)

Yes, it's true.  You can't mix libraries from different versions of
the compiler because the ABI changed.  Make sure you are using the
right library.  This doesn't sounds like that problem.

Another thought.  Compile a simple hello world C++ program with the
new compiler and try to run the executable.  If you get the same
error, then it's a problem with dynamic loading independent of what
python wants.

Presumably, Jeff knows where the fresh library file (libstdc++.so.5)
was installed and can set LD_LIBRARY_PATH accordingly.

-- 
Ricardo Anguiano
CodeSourcery, LLC



More information about the Gcc-help mailing list