On 01/28/2014 01:58 AM, adebayoj wrote:
hello all,
I get the same errors as the ones posted above when I install the package through macports.
dyld: lazy symbol binding failed: Symbol not found: __ZN5boost6python7objects23register_dynamic_id_auxENS0_9type_infoEPFNSt3__14pairIPvS2_EES5_E Referenced from: /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/graph_tool/libgraph_tool_core.so Expected in: flat namespace
dyld: Symbol not found: __ZN5boost6python7objects23register_dynamic_id_auxENS0_9type_infoEPFNSt3__14pairIPvS2_EES5_E Referenced from: /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/graph_tool/libgraph_tool_core.so Expected in: flat namespace Y It builds fine, but when I import graph_tool in python, I get this error. I have tried several different things, but I have not been able to fix it. Is there a stable version we can install through macports?
This is a stable version. The problem is probably due to boost python being compiled against a different python version, or with a different compiler. Questions related to installations through macports are better handled by the macports project. You can submit a bug report at: https://trac.macports.org/auth/login/?next=/newticket They are usually very responsive.
I am new here, but just a suggestion. I have found the installation process for this package to be fraught with so many difficulties. For such a useful package, maybe more effort needs to be invested in making it easily accessible to install. This is perhaps the only advantage I really think networkx has at the moment.
Networkx is a pure python package, and requires no compilation. Graph-tool requires compilation, since the backbone is in C++, and it depends on other C/C++ libraries. Because of this, there will always be more hurdles with graph-tool than with networkx, since all dependencies need to be in place, and much fewer people understand how to set them up. This is made trivial by operating systems which perform automatic dependency tracking, such as virtually any GNU/Linux distro. MacOS lacks this in the OS, but it is provided by macports (and homebrew, and fink), which is a huge help, but it is not perfect, as you have seen. I try to make this easier by offering pre-compiled packages, but it is unfeasible to do this for every OS/Architecture out there. I would make pre-compiled packages for MacOS, since it would quench about 90% of the compilation problems reported to me, but I don't have access to a modern MacOS machine. But I'm always open to constructive suggestions... Best, Tiago -- Tiago de Paula Peixoto <tiago@skewed.de>