[C++-sig] RE: undefined symbol "typeinfo for boost::python::instance_holder " under Linux/RH9

[Langston, Matthew David]

Hi Dave,

Under Linux I simply did a bjam "-sTOOLS=gcc", which created

boost/libs/python/build/bin-stage/libboost_python.a

which bjam appears to have copied (based on file sizes) from

boost/libs/python/build/bin/libboost_python.a/gcc/release/runtime-link-dynamic/libboost_python.a

So, I assume bjam built everything properly. What else to try? Are you saying that statically linking to libboost_python.a on linux/gcc should work? I am using boost 1.30.0, so would upgrading to 1.30.2 maybe help?

-Matt


"Langston, Matthew David" <langston at SLAC.Stanford.EDU> writes:

> Why doesn't statically linking to Boost.Python work under Linux/gcc?
> Thank you for your help.

Not using bjam is usually the explanation for this sort of problem,
but it could just as easily be a compiler bug.

How are you doing the build?

Did you build a static version of Boost.Python to link to
(libboost_python.a)?