Claudio Martella wrote: > ./configure --prefix=/opt/local/ [...]
> configure: error: > Could not link test program to Python. Maybe the main Python library has > been > installed in some non-standard library path. If so, pass it to configure, > via the LDFLAGS environment variable. > Example: ./configure LDFLAGS="-L/usr/non-standard-path/python/lib" > ============================================================================ > ERROR! > You probably have to install the development version of the Python package > for your distribution. The exact name of this package varies among them. > ============================================================================ > > this IS weird. It is always useful to look in config.log to understand what is going on, and in this case it is not so complicated. In the log there is the line configure:16040: gcc -o conftest -g -O2 -I/opt/local/Library/Frameworks/Python.framework/Versions/2.6/include/python2.6 conftest.c -L/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6 -lpython2.6 >&5 ld: library not found for -lpython2.6 Which makes sense, since your python library seems to be /opt/local/lib/libpython2.6.dylib Therefore you need to include /opt/local/lib/ to your linker path. You can do this with LDFLAGS="-L/opt/local/lib". If you think this is annoying, just wait until you get it to start compiling, and the linker starts really spitting errors... :-( Cheers, Tiago
signature.asc
Description: OpenPGP digital signature
_______________________________________________ graph-tool mailing list graph-tool@forked.de http://lists.forked.de/mailman/listinfo/graph-tool
