Hi Tiago

Yes, but no matter what way i build boost it doesn't build libs with -mt:

$ find /home/gs/c/lib/boost-1.53.0//lib | grep python
/home/gs/c/lib/boost-1.53.0//lib/libboost_python.so
/home/gs/c/lib/boost-1.53.0//lib/libboost_python.so.1.53.0
/home/gs/c/lib/boost-1.53.0//lib/libboost_python.a

I thought the -mt lib files are actually a debian packaging thing and not something created by boost

Perhaps i could sym link them all?


On Monday, January 6, 2014 4:41:27 PM UTC, Tiago Peixoto wrote:
On 01/06/2014 03:05 PM, Gerry Steele wrote:
> Hi.
>
> I've looked at previous posts based on similar issues but cannot find anything useful.
>
> I have built boost (1.53.0) using a shared python (2.7) build i built myself. I tried both default boost build as well as ./b2 -j 9 link=static,shared threading=multi
>
> However it still fails to build.
>
> config.log here: https://dpaste.de/dAIW

From your log file:

    /usr/bin/ld: cannot find -lboost_python-mt-2.7

So, the linker cannot find the boost python library, probably because it
has some unexpected name, or because you haven't specified the correct
link paths. Also consider using the --with-boost-python option.

> Input would be appreciated as I can only build in this way without a package manager.
>
> Also note that i had to change some lines in the configure to get it to this point already.
>
> Namely -Wno-unused-local-typedefs and -std=gnu++0x
>
> I'm using gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-48) on RHEL 5.5

I don't think you will be able to compile graph-tool with GCC 4.1... I
think you need at least GCC 4.4.

Best,
Tiago

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