|Summary:||x11-libs/xpyb with python3 - checking for python include dir... File "<string>", line 1 from distutils import sysconfig; print [...]|
|Product:||Gentoo Linux||Reporter:||Jason Lamb <jason>|
|Component:||Current packages||Assignee:||Gentoo X packagers <x11>|
|Severity:||normal||CC:||mgorny, python, throw_away_2002|
|Package list:||Runtime testing required:||---|
complete build log
Description Jason Lamb 2013-02-14 14:00:30 UTC
Comment 1 Jason Lamb 2013-02-14 14:01:10 UTC
Created attachment 338862 [details] emerge --info
Comment 2 Jason Lamb 2013-02-14 14:01:29 UTC
Created attachment 338864 [details] complete build log
Comment 3 Jason Lamb 2013-03-07 19:17:47 UTC
I received this same error today when trying to update x11-libs/xpyb-1.3.1 to x11-libs/xpyb-1.3.1-r1. I was able to complete the emerge by setting the PYTHON_SINGLE_TARGET="python2_7", for both x11-libs/xpyb-1.3.1-r1 and x11-proto/xcb-proto-1.8-r1. Thanks..
Comment 4 Chí-Thanh Christopher Nguyễn 2013-05-01 09:40:20 UTC
*** Bug 461630 has been marked as a duplicate of this bug. ***
Comment 5 Chí-Thanh Christopher Nguyễn 2013-05-01 09:40:37 UTC
*** Bug 468098 has been marked as a duplicate of this bug. ***
Comment 6 Matt Turner 2017-02-27 05:52:32 UTC
Unable to reproduce. Presumably whatever the problem was is long since fixed.
Comment 7 Matt Turner 2017-02-27 06:08:09 UTC
Ah, I see. This was caused by python3, and xpyb mistakenly lost python3 support due a mistake in fixing bug 470902. (I hit the same thing when trying to add python3 support back...)
Comment 8 Michał Górny 2017-02-27 07:54:12 UTC
If you want to pursue it, then I suggest upstreaming a patch switching to standard autotools Python macros instead of that custom broken stuff.