Summary: | app-emulation/virtualbox-1.6.2 headless on ~amd64 fails: kmk failed | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Hilco <hilco.wijbenga> |
Component: | Current packages | Assignee: | Markus Ullmann (RETIRED) <jokey> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | swapon |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | The error with a bit more context. |
Description
Hilco
2008-08-10 06:47:49 UTC
Created attachment 162604 [details]
The error with a bit more context.
(In reply to comment #0) > USE flags: headless -additions -alsa -pulseaudio -sdk Hi, just tested on my amd64 and builds here, unfortunately i'm not using your same profile (and compiler) i'm on: default-linux/amd64/2007.0/desktop (x86_64-pc-linux-gnu-4.1.2). This problem seems related to the hardened gcc profile, could you test it with the gcc 3.4.6-vanilla profile? Okay, I tried both 1.6.2 and 1.6.4 with both vanilla and hardened. Vanilla compiles fine, hardened fails on kmk. So it seems to be a hardened problem. Reassign to Hardened? I can confirm this error on a fresh new Gentoo Hardened 2008.0 amd64 multilib. Using gcc-config to switch to vanilla gcc will compile virtualbox successfully. (In reply to comment #3) [..] (In reply to comment #4) [..] Unluckily there are known problems with VirtualBox and the gcc-hardened profile Please report this stuff also upstream as we're not the only distribution providing hardened toolchains. Sorry that we can't do more about it at the moment Is it safe to use the vanilla compiled version of VirtualBox when the rest of the system was compiled with the hardened toolchain? I am currently also experiencing this problem and I don't want to go back to non-hardened because originally I decided to install hardened because somewhere in the gentoo docs I read that hardened toolchain is the recommended and supported server platform for gentoo. I'm adding the upstream URL for this issue to follow it there: http://www.virtualbox.org/ticket/1262 |