Hi Peter,

I'm not sure - maybe this will help??



On 9 November 2013 01:36, Peter Eastman <peastman@stanford.edu> wrote:
Hi Karl,

Well, the missing symbols are in my own library (the one I'm wrapping with SWIG), not in the C++ standard library.  On the other hand, the differences in how the names get mangled do seem to relate to standard libraries, e.g. "std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >" instead of just "string".  So perhaps it has to do with Python using a different version of the standard library from what I used when compiling?  Is that even possible?  If so, can you tell it which version to use?


On Nov 8, 2013, at 4:22 PM, Karl Wette <karl.wette@gmail.com> wrote:

> Hi Peter,
> I've no idea whether this is related, but I believe MacOSX 10.9 uses a different implementation of the C++ standard library than previous versions. Perhaps your module is trying to load the new library and getting different symbols??
> Cheers,
> Karl