Problems with gcc 3.2

[bjorn rohde jensen]

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