Thanks Tiago, that was indeed the issue.

On Saturday, December 21, 2013 10:22:50 AM UTC, Tiago Peixoto wrote:

Hi,

Whenever reporting problems with building the library, please never
forget to provide some basic information such as which operating system
you are using, what compiler version, and so on. Also please attach a
the _complete_ output of the configure script, together with the file
config.log which is generated.

As the error message below says, the problem occurs because the script
cannot link with the python library. The necessary information required
to understand why the problem happens is included in the config.log
file. But since you seem to have compiled and installed python yourself,
a common source of problems is to forget to compile the python shared
library, which is done by passing "--enable-shared" to the configure
script when compiling python. Please make sure you have done so...

Cheers,
Tiago

On 12/19/2013 02:19 PM, Gerry Steele wrote:
> Thought it might be useful to include this output:
>
> ================
> Detecting python
> ================
> checking whether /home/gs/Python-2.7.6/python-2.7.6/bin/python version is >= 2.6... yes
> checking for /home/gs/Python-2.7.6/python-2.7.6/bin/python version... 2.7
> checking for /home/gs/Python-2.7.6/python-2.7.6/bin/python platform... linux2
> checking for /home/gs/Python-2.7.6/python-2.7.6/bin/python script directory... ${prefix}/lib/python2.7/site-packages
> checking for /home/gs/Python-2.7.6/python-2.7.6/bin/python extension module directory... ${exec_prefix}/lib/python2.7/site-packages
> checking for python2.7... /home/gs/Python-2.7.6/python-2.7.6/bin/python
> checking for a version of Python >= '2.1.0'... yes
> checking for a version of Python == '2.7.6'... yes
> checking for the distutils Python package... yes
> checking for Python include path... -I/home/gs/Python-2.7.6/python-2.7.6/include/python2.7
> checking for Python library path... -L/home/gs/Python-2.7.6/python-2.7.6/lib/python2.7/config -lpython2.7
> checking for Python site-packages path... /home/gs/Python-2.7.6/python-2.7.6/lib/python2.7/site-packages
> checking python extra libraries...  -lpthread -ldl  -lutil
> checking python extra linking flags... -Xlinker -export-dynamic
> checking consistency of all components of python development environment... no
> configure: error: in `/home/gs/graph-tool-2.2.27':
> 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.
>   ============================================================================
>
>
> On Thursday, December 19, 2013 12:44:37 PM UTC, Gerry Steele wrote:
>
>     I've searched the forum repeatedly and not found anything helpful despite this issue being posted 5 or 6 times sadly.
>
>     I'm working in an environment where I need to build all dependencies from scratch. I've failed at the first hurdle with:
>
>     > 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.
>
>     Note I have built the python install i need to use myself. So when i try:
>
>     $ ./configure --prefix=`pwd`/gt-inst  LDFLAGS="-L/home/gs/Python-2.7.6/python-2.7.6/lib/python2.7/lib"
>
>     Or similar i just get the same error.
>
>     What is different about the python install graph-tool configure expects?
>
>     Thanks
>     Gerry
>
>
>
> _______________________________________________
> graph-tool mailing list
> graph...@skewed.de
> http://lists.skewed.de/mailman/listinfo/graph-tool
>


--
Tiago de Paula Peixoto <ti...@skewed.de>