Hi Bart,
[..]
> check to which python your libboost_python.dylib is linked to:
> $ otool -L libboost_python.dylib
> libboost_python.dylib:
> libboost_python.dylib (compatibility version 0.0.0, current version
> 0.0.0)
> /System/Library/Frameworks/Python.framework/Versions/2.6/Python
> (compatibility version 2.6.0, current version 2.6.1)
> /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current
> version 7.9.0)
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
> version 125.0.0)
>
> In my case as shown above (in blue) it was still linked to the old python (in
> Python.frameworks)
> So I changed it (using install_name_tool) to my new python (in
> MyPython.framework which I have built from source) as follows:
> $ sudo install_name_tool -change
> /System/Library/Frameworks/Python.framework/Versions/2.6/Python
> /Library/Frameworks/MyPython.framework/Versions/2.6/MyPython
> libboost_python.dylib
That was the problem - thanks a lot! Somehow Boost is always linking against
the system python. Maybe someone knows how to get Boost to link against another
version? That should also be in the wiki.
I did not build my own python but used the stock python from python.org.
Smithers:examples markus$ sudo install_name_tool -change
/System/Library/Frameworks/Python.framework/Versions/2.6/Python/Library/Frameworks/Python.framework/Versions/2.6/Python
libboost_python.dylib
Worked as well. I think this makes things easier when you update or install
other packages.
Thanks for the quick help!
Markus
_______________________________________________
PyOpenCL mailing list
[email protected]
http://tiker.net/mailman/listinfo/pyopencl_tiker.net
