Hi Tiago,
I re-homebrew-ed boost 1.47 and now otool shows linkage to homebrew-ed python.
Still graph-tool is linked to Xcode's python (even exporting DYLD_LIBRARY_PATH
your way).
Anyway, I tried importing again graph_tool and this time I've got a new problem
:)
In [1]: from graph_tool.all import *
---------------------------------------------------------------------------
ImportError Traceback (most recent call last)
/Users/hammer/TIS/java-hacking/twitter/src/<ipython-input-1-100bbe2bc9d9> in
<module>()
----> 1 from graph_tool.all import *
/usr/local/Cellar/python/2.7.2/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/graph_tool/__init__.py
in <module>()
90
91 from dl_import import *
---> 92 dl_import("import libgraph_tool_core as libcore")
93 import libgraph_tool_core as libcore # for pylint
94 __version__ = libcore.mod_info().version
/usr/local/Cellar/python/2.7.2/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/graph_tool/dl_import.pyc
in dl_import(import_expr)
50 sys.setdlopenflags(dl_flags)
51
---> 52 exec import_expr in local_dict, global_dict
53
54 sys.setdlopenflags(orig_dlopen_flags) # reset it to normal case to
avoid
/Users/hammer/TIS/java-hacking/twitter/src/<string> in <module>()
ImportError:
dlopen(/usr/local/Cellar/python/2.7.2/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/graph_tool/libgraph_tool_core.so,
8): Library not loaded: /usr/local/lib/libboost_thread-mt.dylib
Referenced from: /usr/local/lib/libCGAL.8.0.0.dylib
Reason: image not found
which is correct as:
$ ls -l /usr/local/lib/libboost_thread-mt.dylib
ls: /usr/local/lib/libboost_thread-mt.dylib: No such file or directory
Apparently the only dylib missing is that for thread_mt.
Any idea what's going on?
--
Claudio Martella
[email protected]
On Dec 30, 2011, at 7:16 PM, Tiago de Paula Peixoto wrote:
> 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 <[email protected]>
>
> _______________________________________________
> graph-tool mailing list
> [email protected]
> http://lists.skewed.de/mailman/listinfo/graph-tool
_______________________________________________
graph-tool mailing list
[email protected]
http://lists.skewed.de/mailman/listinfo/graph-tool
