On 12/30/2011 03:44 PM, Martella, C. wrote:
true! don't know why it passed my otool -L libboost* | grep python.
$ otool -L libboost_python-mt.dylib libboost_python-mt.dylib: /usr/local/lib/libboost_python-mt.dylib (compatibility version 0.0.0, current version 0.0.0) /System/Library/Frameworks/Python.framework/Versions/2.7/Python (compatibility version 2.7.0, current version 2.7.1) /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 52.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 159.0.0)
Should I also build again libboost by myself (instead of using the homebrew version)?
No, I think the problem is happening at runtime...
I must admit i'm pretty unfamiliar with DYLD_LIBRARY_PATH. Should I set it at compile time or runtime?
Runtime. The variable tells the runtime linker where the shared libraries are located. Try the following: export DYLD_LIBRARY_PATH="$DYLD_LIBRARY_PATH:/usr/local/Cellar/python/2.7.2/Frameworks/Python.framework/Versions/2.7/lib/python2.7" And then run the same otool commands as before. Cheers, Tiago -- Tiago de Paula Peixoto <tiago@skewed.de>