Hi Tiago,
to be honest, I can't see how lib boost can be linked to python. I ldd it and
couldn't find any linkage to python.
But the problem is indeed with libgraphtool being linked to Xcode python:
$ otool -L libgraph_tool_core.so
libgraph_tool_core.so:
/System/Library/Frameworks/Python.framework/Versions/2.7/Python
(compatibility version 2.7.0, current version 2.7.1)
/usr/local/lib/libboost_iostreams-mt.dylib (compatibility version
0.0.0, current version 0.0.0)
/usr/local/lib/libboost_python-mt.dylib (compatibility version 0.0.0,
current version 0.0.0)
/usr/local/lib/libboost_regex-mt.dylib (compatibility version 0.0.0,
current version 0.0.0)
/usr/lib/libexpat.1.dylib (compatibility version 7.0.0, current version
7.2.0)
/usr/local/lib/libCGAL.8.0.0.dylib (compatibility version 8.0.0,
current version 8.0.0)
/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.1.0)
I don't get why/how it happened. Any idea?
--
Claudio Martella
[email protected]
On Dec 30, 2011, at 5:17 PM, Tiago de Paula Peixoto wrote:
> On 12/30/2011 11:02 AM, Martella, C. wrote:
>> Hi Tiago,
>>
>> thanks for the quick fix. I've been able to configure and build it
>> successfully. the import now works but I get the same interpreter
>> mismatch error as before. I'm using homebrew for building both python,
>> cgal, graphviz, boost, numpy and scipy and they are all built with
>> apple gcc 4.2 and linked to the homebrewed python in /usr/local/.
>>
>> Here's the error by the interpreter:
>> Fatal Python error: Interpreter not initialized (version mismatch?)
>> Abort trap: 6
>>
>> I've checked for the configure output of graph_tool, and there's
>> something which it might be creating problems:
>>
>
> [...]
>
>> For what I can see the python libs are correctly found in /usr/local/ except
>> for these lines:
>>
>> checking for python2.7/Python.h... yes
>> results of the Python check:
>> Binary: python2.7
>> Library: python2.7
>> Include Dir:
>> /Developer/SDKs/MacOSX10.7.sdk/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7
>>
>>
>> where apparently the original Xcode python is found. why's that? do
>> you have any suggestions on configure options for it to stick it to
>> the correct versions? i've tried some options based on python-config
>> but unsuccessfully.
>> By looking at the way graph_tool is built, i don't really get what's
>> going on, because both -I and -L options are /usr/local/ paths. I
>> attach here the config.log, hoping it can help.
>
> By looking at your config.h, it seems that the paths are in order:
>
> #define PYTHON_DIR
> "/usr/local/Cellar/python/2.7.2/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages"
> #define CXXFLAGS " -Wall -ftemplate-depth-150 -Wno-deprecated
> -Wno-unknown-pragmas -O99 -fvisibility=default -fvisibility-inlines-hidden
> -Wno-unknown-pragmas"
> #define CPPFLAGS "
> -I/usr/local/Cellar/python/2.7.2/Frameworks/Python.framework/Versions/2.7/include/python2.7
> -I/usr/local/include
> -I/usr/local/Cellar/python/2.7.2/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/numpy/core/include/numpy
>
> -I/usr/local/Cellar/python/2.7.2/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/scipy"
> #define LDFLAGS "
> -L/usr/local/Cellar/python/2.7.2/Frameworks/Python.framework/Versions/2.7/lib/python2.7
> -lpython2.7"
>
> You should check if the compiled binary is indeed linked with the
> correct python library. You should do the same check with your
> boost-python library.
>
> 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
