Created attachment 310779 [details] build.log (libgsf-1.14.22, .23 fails similarly). libgsf's python bindings are pygobject-based, and pygobject currently is not built for pypy. This causes libgsf with USE=python and 2.7-pypy-1.8 in USE_PYTHON to fail confusingly, as the configure phase tries to use pypy as python. config.log: configure:15195: checking for headers required to compile python extensions configure:15210: x86_64-pc-linux-gnu-gcc -E -I/usr/lib64/pypy1.8/include/python2.7 conftest.c conftest.c:49:20: fatal error: Python.h: No such file or directory but this does not cause configure to actually fail. The build does later on though: * Building of gnome-extra/libgsf-1.14.22 with CPython 2.7... make -j4 PYTHON_INCLUDES=-I/usr/include/python2.7 pyexecdir=/usr/lib64/python2.7/site-packages pythondir=/usr/lib64/python2.7/site-packages (cd . \ && \ --load-types gsf-arg-types.py \ --override gsf.override \ --prefix pygsf gsf.defs) > gen-gsf.c \ && cp gen-gsf.c gsf.c \ && rm -f gen-gsf.c CC _gsfmodule_la-gsfmodule.lo /bin/sh: line 2: --load-types: command not found make: *** [gsf.c] Error 127 make: *** Waiting for unfinished jobs.... gsfmodule.c:25:23: fatal error: pygobject.h: No such file or directory compilation terminated. make: *** [_gsfmodule_la-gsfmodule.lo] Error 1 The way the build fails is a bit messy (there might be some improvements possible there), but the right thing to do seems to be just adding *-pypy-* to RESTRICT_PYTHON_ABIS, as there's no way this will work without pygobject built for pypy. The package builds fine with that change.
Feel free to commit it yourself if you have time
Fixed, thanks for reporting. > 05 May 2012; Alexandre Rostovtsev <tetromino@gentoo.org> > libgsf-1.14.21.ebuild, libgsf-1.14.22.ebuild, libgsf-1.14.23.ebuild: > Restrict pypy python ABI (bug #414587, thanks to Marien Zwart). Update to > virtual/pkgconfig.
