Summary: | app-emulation/virtualbox-4.0.2 fails to compile | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Waldemar Szostak <wszostak> |
Component: | Current packages | Assignee: | Lars Wendler (Polynomial-C) (RETIRED) <polynomial-c> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | bkohler, kripton, patrick, proxy-maint, swapon |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Waldemar Szostak
2011-02-12 16:57:27 UTC
Is 'threads' useflag set for the 2.6 and 2.7 too ? (In reply to comment #1) > Is 'threads' useflag set for the 2.6 and 2.7 too ? > Hmm, it is for 2.7, not for 2.6, though. I recompiled 2.6 and virtualbox afterwards, and it worked. Dzięki za wskazówkę! ;) Anyway, I guess the ebuild should detect this kind of problems, shouldn't it? Another interesting thing is that 'emerge -avNDu world' doesn't detect it, but when I ran 'emerge -pv "=dev-lang/python-2.6.6-r1" "=dev-lang/python-2.7.1"' the 'threads' USE flag is highlighted to have changed... Should I report a bug for portage because of this? So what's the exact problem here? Does virtualbox generally need python with threads USE flag being enabled or just some specific version of python? Well, the problem here is that with multiple python abis, portage still checks for only one positive python[threads] - if the flags differ between slots, this will fail on a python[-threads] instance. It's a portage deficiency, arguably a bug. I believe this was fixed some time ago with the move to python-r1 eclasses, see bug #311199 to be sure. *** This bug has been marked as a duplicate of bug 311199 *** |