Summary: | >=app-emulation/virtualbox-modules-4.1.0-r1 fails to compile with >=sys-kernel/hardened-sources-2.6.39-r9 and > sys-devel/gcc-4.4.5 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Enoid <genoid> |
Component: | [OLD] Unspecified | Assignee: | Lars Wendler (Polynomial-C) (RETIRED) <polynomial-c> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | hardened-kernel+disabled, patrick, radegand, swapon |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://forums.virtualbox.org/viewtopic.php?p=197250 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
constification.patch
virtualbox-modules-4.1.2-bug379421.patch |
Description
Enoid
2011-08-16 15:45:13 UTC
Created attachment 283571 [details, diff]
constification.patch
I've also hit this bug and I can confirm that the attached patch allowed virtualbox-modules to compile. Is this still a problem with virtualbox-modules-4.1.2.ebuild? (In reply to comment #3) > Is this still a problem with virtualbox-modules-4.1.2.ebuild? Yes, I still cannot compile virtualbox-modules-4.1.2 on hardened-sources-2.6.39-r11. In the same time I can confirm that it compiles fine on hardened-sources-2.6.39-r8. (In reply to comment #3) > Is this still a problem with virtualbox-modules-4.1.2.ebuild? I can confirm it too, still the same problem. I did some additional testing and tried to compile the patched version with 2.6.39-r8 and it fails, which is suspected as the code that the patch adds isn't compatible with that specific kernel revision. So there should be a check for the specific revision of the hardened-sources that is used. I couldn't find a predefined way to do this though... Or the 'pax_kernel' use flag could be added. I know mesa and some others use it to fix hardened-sources problems. But again, there should be a specific kernel revision check, otherwise it will fail on everthing below -r9. Let's add the hardened-kernel team. I don't want to add patches that might make the virtualbox-modules incompatible to non-hardened kernels and they maybe can shed some more light into this... (In reply to comment #6) > Let's add the hardened-kernel team. I don't want to add patches that might make > the virtualbox-modules incompatible to non-hardened kernels and they maybe can > shed some more light into this... This is supposed to be fixed in the later version of 2.6.39 (try -r12), however there is another bug on x86 that needs to be resolved before stabilizing the higher -rX's. See bug #378731, comments #5 and #7. Can you test on hardened-sources-2.6.39-r12 without modifying vboxhost/vboxdrv/SUPDrvIDC.h and report back. (In reply to comment #7) > Can you test on hardened-sources-2.6.39-r12 without modifying > vboxhost/vboxdrv/SUPDrvIDC.h and report back. The build still fails for me with -r12. (In reply to comment #7) > Can you test on hardened-sources-2.6.39-r12 without modifying > vboxhost/vboxdrv/SUPDrvIDC.h and report back. Unfortunately, at the moment I can't compile 2.6.39-hardened-r12 on amd64, see https://bugs.gentoo.org/show_bug.cgi?id=378731#c18 (In reply to comment #9) > (In reply to comment #7) > > Can you test on hardened-sources-2.6.39-r12 without modifying > > vboxhost/vboxdrv/SUPDrvIDC.h and report back. > > Unfortunately, at the moment I can't compile 2.6.39-hardened-r12 on amd64, see > https://bugs.gentoo.org/show_bug.cgi?id=378731#c18 Please use gcc-4.4.5 (In reply to comment #10) > Please use gcc-4.4.5 Hi, Indeed, I can confirm that virtualbox-modules-4.1.2 compiles fine on hardened-sources-2.6.39-r12 using gcc-4.4.5 (and fails with gcc-4.5.3-r1) (In reply to comment #11) > Indeed, I can confirm that virtualbox-modules-4.1.2 compiles fine on > hardened-sources-2.6.39-r12 using gcc-4.4.5 (and fails with gcc-4.5.3-r1) For the record - it also compiles fine with gcc-4.4.6-r1 which is the latest gcc-4.4.x in portage tree. Created attachment 287873 [details] virtualbox-modules-4.1.2-bug379421.patch Now when sys-devel/gcc-4.5.3-r1 is table it would be nice to apply that patch because all versions of virtualbox including the stable one are broken. FYI, the problem is fixed in the next version app-emulation/virtualbox-modules-4.1.4 *** This bug has been marked as a duplicate of bug 386497 *** |