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> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | mgorny, python, throw_away_2002 |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge --info
complete build log |
Description
Jason Lamb
2013-02-14 14:00:30 UTC
Created attachment 338862 [details]
emerge --info
Created attachment 338864 [details]
complete build log
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.. *** Bug 461630 has been marked as a duplicate of this bug. *** *** Bug 468098 has been marked as a duplicate of this bug. *** Unable to reproduce. Presumably whatever the problem was is long since fixed. 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...) If you want to pursue it, then I suggest upstreaming a patch switching to standard autotools Python macros instead of that custom broken stuff. |