on Fri Dec 12 2008, "Rocketman-AT-JSC" <smnemeth-AT-gmail.com> 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 to make sure that build/test works. The library you build and the one linked to by the tutorial should be identical, apart from SONAME and associated mangling. > 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 > objdump: > > /ips/fd/analysis2/proto/oss/lib $ ls libboost_python-* > libboost_python-gcc32-mt-1_35.so libboost_python-gcc32-mt-d.so > libboost_python-il-mt-1_36.so.1.36.0 > libboost_python-gcc32-mt-1_35.so.1.35.0 libboost_python-gcc32-mt.so > libboost_python-il-mt.a > libboost_python-gcc32-mt-d-1_35.so libboost_python-il-mt-1_36.a > libboost_python-il-mt.so > libboost_python-gcc32-mt-d-1_35.so.1.35.0 libboost_python-il-mt-1_36.so > > /ips/fd/analysis2/proto/oss/lib $ objdump -t libboost_python-il-mt*.so | > grep throw_error_already_set > > /ips/fd/analysis2/proto/oss/lib $ objdump -t libboost_python-gcc32-mt.so | > grep throw_error_already_set > > /ips/fd/analysis2/proto/oss/lib $ objdump -t libboost_python-gcc32-mt-d.so | > grep throw_error_already_set > 0009cd14 g F .text 0000007c > _ZN5boost6python23throw_error_already_setEv This doesn't make any sense to me. I don't see the string "throw_error_already_set" in the grep output. is this really what came up on your console? Anyway, I think you need to use objdump -T/--dynamic-syms, not objdump -t/--syms. The non-debug ones don't show /any/ symbols if you use -t. -- Dave Abrahams BoostPro Computing http://www.boostpro.com _______________________________________________ Cplusplus-sig mailing list Cplusplus-sig@python.org http://mail.python.org/mailman/listinfo/cplusplus-sig
