The ebuild does not use the Python ABI functionality of Portage nor does it specify which Python version to build with. By default, this package's build system is grabbing whatever is /usr/bin/python and then breaks during a later test: checking for a Python interpreter with version >= 2.2... python checking for python... /usr/bin/python checking for python version... 3.1 checking for python platform... linux2 checking for python script directory... ${prefix}/lib64/python3.1/site-packages checking for python extension module directory... ${exec_prefix}/lib64/python3.1 /site-packages checking for headers required to compile python extensions... File "<string>", line 1 import sys; print sys.prefix ^ SyntaxError: invalid syntax File "<string>", line 1 import sys; print sys.exec_prefix ^ SyntaxError: invalid syntax Manually specifying each Python version for configure should solve this problem.
like most other gnome packages, yes we know, thanks.
Created attachment 233469 [details] ebuild.diff This enables it to install with python 3 set as active python version.
(In reply to comment #2) > Created an attachment (id=233469) [details] > ebuild.diff This patch applies to the 2.10.0 version in the gnome overlay, too. I would drop some versions infos which were met by all tree version additionally. Thanks for the patch dabott!
*** This bug has been marked as a duplicate of bug 345521 ***
