This causes problems during pre-reboot module rebuild for new kernel. The workaround is: 1. Build new kernel 2. Reboot 3. Then rebuild modules and load them manually Which is error-prone.
What version does this happen on? Can you attach the full build log? I cannot reproduce this on my machines.
(In reply to Ben Kohler from comment #1) > What version does this happen on? Can you attach the full build log? I > cannot reproduce this on my machines. Ups. Sorry I meant app-emulation/virtualbox-guest-additions. In any case - I had troubles with 4.2.something. I could not reproduce on 4.3.
# emerge virtualbox-guest-additions Calculating dependencies... done! >>> Verifying ebuild manifests >>> Emerging (1 of 1) app-emulation/virtualbox-guest-additions-4.2.18 * VirtualBox-4.2.18.tar.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found sources for kernel version: * 3.10.17-gentoo >>> Unpacking source... <SNIP, emerge completes successfully> # eselect kernel show Current kernel symlink: /usr/src/linux-3.10.17-gentoo # uname -r 3.12.1-gentoo # qlist virtualbox-guest-additions | grep modules /lib/modules/3.10.17-gentoo/misc/vboxguest.ko /lib/modules/3.10.17-gentoo/misc/vboxsf.ko # I still cannot reproduce this issue, can you reproduce it now? Are you doing something like setting KBUILD_OUTPUT to build out of the main source dir?