Summary: | app-emulation/virtualbox-{ose,bin}-2.1.4 stabling (previous stable doesn't build with gcc-4.3) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Patrick Lauer <patrick> |
Component: | New packages | Assignee: | Markus Ullmann (RETIRED) <jokey> |
Status: | RESOLVED LATER | ||
Severity: | normal | CC: | andrey.vihrov, denilsonsa, DuPol, maxicombina, swapon, volkmar |
Priority: | High | Keywords: | STABLEREQ |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 267310 |
Description
Patrick Lauer
2009-04-23 20:42:02 UTC
I have been using 2.1.4 on stable amd64 for two months already and have encountered no issues. Contrary to that, the current stable 1.6.6 hangs if I suspend my laptop with a VM running (at least this was true with 2.6.27). So, another vote for a newer stable version here. >>> Completed installing xf86-input-virtualbox-2.1.4 into /var/tmp/portage/x11-drivers/xf86-input-virtualbox-2.1.4/image/
* QA Notice: Pre-stripped files found:
* /usr/lib/xorg/modules/input/vboxmouse_drv.so
Files matching a file type that is not allowed:
usr/lib/xorg/modules/input/vboxmouse_drv.so
*
* ERROR: x11-drivers/xf86-input-virtualbox-2.1.4 failed.
* Call stack:
* misc-functions.sh, line 729: Called install_qa_check
* misc-functions.sh, line 466: Called die
* The specific snippet of code:
* [[ ${abort} == yes ]] && die "multilib-strict check failed!"
* The die message:
* multilib-strict check failed!
(In reply to comment #2) > * QA Notice: Pre-stripped files found: > * /usr/lib/xorg/modules/input/vboxmouse_drv.so > Files matching a file type that is not allowed: > usr/lib/xorg/modules/input/vboxmouse_drv.so What does that mean? > * The die message: > * multilib-strict check failed! Stupid check ;) I've had a look at the build system, now I want a stiff drink. bug 266756 is critical because gcc 4.3 is now stable and no stable version of virtualbox-ose can be used with a stable profile. The bug has been fixed upstream in 2.1.0 [1]. [1] http://www.virtualbox.org/ticket/936 *** Bug 266756 has been marked as a duplicate of this bug. *** Markus (jokey): Any advice on comment #2? Come again, when you fixed this. |