Shouldn't portage figure out following dependency error situation on its own already before it hits this other check? >>> Emerging (1 of 2) dev-python/wxpython-2.6.4.0-r2 * wxPython-src-2.6.4.0.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * CPV: dev-python/wxpython-2.6.4.0-r2 * REPO: gentoo * USE: amd64 elibc_glibc kernel_linux multilib opengl unicode userland_GNU >>> Unpacking source... >>> Unpacking wxPython-src-2.6.4.0.tar.bz2 to /var/tmp/portage/dev-python/wxpython-2.6.4.0-r2/work >>> Source unpacked in /var/tmp/portage/dev-python/wxpython-2.6.4.0-r2/work >>> Preparing source in /var/tmp/portage/dev-python/wxpython-2.6.4.0-r2/work/wxPython-src-2.6.4.0/wxPython ... * Applying scripts-multiver-2.6.1.0.diff ... [ ok ] >>> Source prepared. >>> Configuring source in /var/tmp/portage/dev-python/wxpython-2.6.4.0-r2/work/wxPython-src-2.6.4.0/wxPython ... * Checking wxGTK-2.6 for X support ... [ !! ] * check_wxuse - You have requested functionality that requires X support to * have been built into x11-libs/wxGTK. * * Please re-merge =x11-libs/wxGTK-2.6* with the X USE flag enabled. * ERROR: dev-python/wxpython-2.6.4.0-r2 failed: * Missing USE flags. Now, if we change the dependency >=x11-libs/wxGTK-${PV}:2.6[opengl?] into >=x11-libs/wxGTK-${PV}:2.6[X,opengl?] portage is smart enough to figure that out before it bangs its head against that (pre-USE-deps era?) check while emerging stuff. And while we're at it, at least 2.8.10.1 from 2.8 series suffers from the same issue. I didn't try with the latest ~arch one.
Can you please paste an emerge -pv wxpython output?
Sorry for the slow response. The USE flags for the problem situation were following: [ebuild N ] x11-libs/wxGTK-2.6.4.0-r6 USE="odbc opengl unicode -X -debug -doc -gnome -pch -sdl" 18,617 kB [ebuild N ] x11-libs/wxGTK-2.8.10.1-r5 USE="gstreamer odbc opengl -X -debug -doc -gnome -pch -sdl" 29,074 kB I think it was about the stupid combination of USE="-X opengl", which I sorted out later by simply disabling also the opengl flag. I'm closing this as INVALID. There is an inconvenient situation, but I don't think it is fixable with current USE flag and dependency system. I don't know of any way to say that these two USE flags must be enabled in tandem (short of the "depending on itself"-trick mentioned on the dev list the other day, but it is such a hack that it will likely backfire badly).
I'm pretty sure wxpython does require wxGTK built with X, so this is valid.
Since this got reopened I'm fixing my mistake in comment #2. I just realized that I only copy-pasted the wxGTK flags, not the actual wxpython flags asked for in comment #1: [ebuild R ] dev-python/wxpython-2.6.4.0-r2 USE="opengl unicode" 0 kB [ebuild NS ] dev-python/wxpython-2.8.10.1 [2.6.4.0-r2] USE="opengl -cairo -doc -examples" 0 kB
it looks like i already fixed this in 2.8.11.0, i just forgot the stable versions.
Fixed.
