Re: [C++-sig] boost::python::throw_error_already_set not in library

Problem Solved: The symbols are in the shared object, and as David mentioned, one must use the -T to see them in a debug library. The problem was with the intel linker (via eclipse). Apparently the linker will not tell you whether a shared library is actually included using -l to add to a shared

Re: [C++-sig] boost::python::throw_error_already_set not in library

on Fri Dec 12 2008, "Rocketman-AT-JSC" wrote: > Yes it's probably user error--but I have no clue why this is happening. I > did not do the build and the guy doing the build is not an expert boost user > either. Did he use bjam? You can verify the build by following the Boost.Python tutorial

Re: [C++-sig] boost::python::throw_error_already_set not in library

Yes it's probably user error--but I have no clue why this is happening. I did not do the build and the guy doing the build is not an expert boost user either. We have two builds one with gcc and one with intel. Notice the non-debug versions don't have the symbol. Here are the results from objd

Re: [C++-sig] boost::python::throw_error_already_set not in library

on Fri Dec 12 2008, "Rocketman-AT-JSC" wrote: > Seems like this function only gets built into the debug version. Are you certain? It's hard to imagine that's actually the case. > We built the gcc library for 1.35 and it only appears in the > libboost_python_gcc32-mt-d-1_35 version. How did

[C++-sig] boost::python::throw_error_already_set not in library

Seems like this function only gets built into the debug version. We built the gcc library for 1.35 and it only appears in the libboost_python_gcc32-mt-d-1_35 version. Does anyone know why this does not get built into the non-debug version or how to make it get built in? TIA, Scott -- View th