You should pass the option "--with-boost-python=-3-mt" to the configure script, telling it what suffix should be used.
There is no standard naming across systems, and the configure script tries some common ones, but it seems to be failing in this case.
Great, that worked. Is it possible to link more than one version of python? I tried passing ./configure both switches, but only the second instance takes effect: -lboost_python-3.3-mt -lboost_python-2.7-mt (test case works for py2.7, 3.3 fails with 'undefined symbol') -lboost_python-2.7-mt -lboost_python-3.3-mt (test case works for py3.3, 2.7 fails with 'undefined symbol') test case: python -c 'import graph_tool ; print(graph_tool.__version__)' Either way, I was able to get both 2.7 and 3.3 working at the same time by modifying the ebuild since it already handles the individual ./configure scripts for all python versions that are available. Thanks! -Justin