Summary: | x11-drivers/xf86-video-virtualbox-4.1.4 fails to load if compiled with hardened gcc | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Faustus <orlovm> |
Component: | Hardened | Assignee: | The Gentoo Linux Hardened Team <hardened> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | Hugo.Mildenberger, jens |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=332285 https://bugs.gentoo.org/show_bug.cgi?id=352843 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 332285 | ||
Bug Blocks: | 350475 |
Description
Faustus
2011-12-14 23:20:28 UTC
Any comment? This seems like a necessary and simple fix on hardened. *** Bug 352843 has been marked as a duplicate of this bug. *** Faustus, I'd like thank you very much for this analysis. I've successfully tested your proposals with xf86-video-virtualbox-4.1.8 (together with the still masked virtualbox-guest-additions-4.1.8 and xorg-server-1.11.4) on amd64. Apart from fancy desktop effects, Gentoo Hardened was then running very smoothly within a Vista host machine. For others to find this bug, the xorg message on that particular system was "undefined symbol: vgaHWFreeHWRec". There is a somewhat related report at https://bugs.freedesktop.org/show_bug.cgi?id=41208. Therein, the author found a workaround consisting in preloading modules in a certain sequence, which may be also an option if recompilation of xf86-video-virtualbox-4.1.8 can't be done for some reasons. Have updated xf86-video-virtualbox-4.1.8 with a patch for link with lazy The patch is in stable for a long time now, so closing. this patch causes users with non-hardened gcc to fail in emerging this package at the prepare phase. I had to comment out this patch in the .ebulld file and update the digest to emerge this package. Again im not using a hardened kernel or hardened gcc and this caused my emerge of the x11-drivers/xf86-video-virtualbox-4.3.4 to fail in the prepare phase when it got to applying the patches. The other patches were successful but link-lazy.patch wasn't. So I saw that patch was for hardened-kernels. I commented out that code to apply it and now it compiles. (In reply to Christopher Jones from comment #6) > this patch causes users with non-hardened gcc to fail in emerging this > package at the prepare phase. I had to comment out this patch in the .ebulld > file and update the digest to emerge this package. Again im not using a > hardened kernel or hardened gcc and this caused my emerge of the > x11-drivers/xf86-video-virtualbox-4.3.4 to fail in the prepare phase when it > got to applying the patches. The other patches were successful but > link-lazy.patch wasn't. So I saw that patch was for hardened-kernels. I > commented out that code to apply it and now it compiles. Open a new bug The patch need a update to work on 4.3.4 The patch is for the hardened toolchain and it needed else will the virtualbox video driver fail to load as in this bug. (In reply to Magnus Granberg from comment #7) > (In reply to Christopher Jones from comment #6) > > this patch causes users with non-hardened gcc to fail in emerging this > > package at the prepare phase. I had to comment out this patch in the .ebulld > > file and update the digest to emerge this package. Again im not using a > > hardened kernel or hardened gcc and this caused my emerge of the > > x11-drivers/xf86-video-virtualbox-4.3.4 to fail in the prepare phase when it > > got to applying the patches. The other patches were successful but > > link-lazy.patch wasn't. So I saw that patch was for hardened-kernels. I > > commented out that code to apply it and now it compiles. > Open a new bug > The patch need a update to work on 4.3.4 > The patch is for the hardened toolchain and it needed else will the > virtualbox video driver fail to load as in this bug. Bug #494478 |