Maybe a combination of your configuration (profile? /etc/portaga/package* ?) and outdated portage - the oldest ebuild on my freshly updated system is 4.1.24. mpc may be needed for pulseaudio. The ebuild also doesn't list anything about gcc or hardened requirements.

Is there a reason virtualbox requires gcc update and hardened kernel?
And what is mpc?

Could very well be on the gcc update, if gcc-config -l showed 4.6 set, yes? Dep tree shows >=gcc-4.5 on x86 for Virtualbox 4.1.24 here. My guess would be you synced sometime in the past when gcc-4.6 was available along with Virtualbox 4.1.22, but didn't do a full update on world. So, most likely, a necessary update on gcc-4.6 (due to mpc) had to take place before portage allowed Virtualbox to rebuild.

Quote:

dev-lib/mpc Description from portage: A library for multiprecision complex arithmetic with exact rounding.

It's listed as a current dependency of gcc 4.5/6. I have had violent allergic reactions, particularly via horror to eardrums and fits of kernel oopses, on any variants of pulseaudio in the past and present, so it's never been on any of my gentoo builds.

Nothing else looked unusual to me there other than hardened sources being pulled in which I don't have an easy explanation for. Something showing odd in your world file or profile setting? Pulled any rabbits out of a hat lately? Either way, neat trick. And as mentioned, Virtualbox-4.1.22 shouldn't have been in a current sync (removed for .24) on the date of your post._________________Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn.

I believe I'm stumped on this one. I missed the memo on modules-rebuild having never used that script. I don't even recall seeing it mentioned somewhere. Looks like it may work well.

Anyway, grabbing at some straws, you're not using genkernel, correct? Please show the output of the following:

Code:

cat /var/lib/module-rebuild/moduledb

and

Code:

ls -al /lib/modules

and while we're at it (with gentoolkit installed),

Code:

equery l -f '^.*kernel.*$'

along with

Code:

ls -al /usr/src

Finally, what does the --tree (-t) option show on your emerge of virtualbox? Just looking to see a confirm that it is somehow making those hardened sources a dependency (which seems odd if you've installed from gentoo-sources). The virtualbox-modules does have the virtual/linux-sources-0 dependency to ensure that you have some sort of kernel source installed to build against._________________Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn.

Please note the date. You can see what appears to be the relevant *old* bug here. Another hint is on the mailing list archives.

I don't know when you've synced, world updated, revdep-rebuilt, and depcleaned but I would suspect it has been at least a month due to kernel 3.6.11's removal from the tree. The fact of the profile you have selected and the version of virtualbox you're trying to emerge makes me err on the side that you've been trying to work with the system even though your kernel looks to be out of date and has security revision issues you should address. Emerging sys-kernel/gentoo-sources-3.6.11-r1 (which would already happen on a emerge -avuND @world update) and building that patched kernel would resolve those issues.

So, check for that old virtual ebuild being in your world file as I suspect it may be. There is no particular reason for virtual/linux-sources to be in your world file especially when it's an abandoned ebuild, it isn't in any of mine.

Code:

grep -i virtual /var/lib/portage/world

Remove it,

Code:

emerge -C virtual/linux-sources-2.6

Or simply delete the respective line from /var/lib/portage/world and then make sure you've emerge --sync'ed. Then show another emerge -pvt of virtualbox. Again, it would be in your best interests to do a full emerge -uvND @world update._________________Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn.