compiling vairtualbox-modules gives this error [ebuild R ~] app-emulation/virtualbox-modules-4.2.16 USE="-pax_kernel" 0 kB Total: 1 package (1 reinstall), Size of downloads: 0 kB >>> Verifying ebuild manifests >>> Emerging (1 of 1) app-emulation/virtualbox-modules-4.2.16 * vbox-kernel-module-src-4.2.16.tar.xz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found kernel object directory: * /lib/modules/3.10.4/build * Found sources for kernel version: * 3.10.4 >>> Unpacking source... >>> Unpacking vbox-kernel-module-src-4.2.16.tar.xz to /tmp/tmerge/portage/app-emulation/virtualbox-modules-4.2.16/work >>> Source unpacked in /tmp/tmerge/portage/app-emulation/virtualbox-modules-4.2.16/work >>> Preparing source in /tmp/tmerge/portage/app-emulation/virtualbox-modules-4.2.16/work ... >>> Source prepared. >>> Configuring source in /tmp/tmerge/portage/app-emulation/virtualbox-modules-4.2.16/work ... >>> Source configured. >>> Compiling source in /tmp/tmerge/portage/app-emulation/virtualbox-modules-4.2.16/work ... ln: failed to create symbolic link 'Module.symvers': File exists * Preparing vboxdrv module make -j5 -l4 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- 'LDFLAGS=-m elf_x86_64' KERN_DIR=/usr/src/linux KERNOUT=/lib/modules/3.10.4/build all *** Building 'vboxdrv' module *** make[1]: Entering directory `/tmp/tmerge/portage/app-emulation/virtualbox-modules-4.2.16/work/vboxdrv' Makefile:190: *** Error: KERN_DIR does not point to a directory. Stop. make[1]: Leaving directory `/tmp/tmerge/portage/app-emulation/virtualbox-modules-4.2.16/work/vboxdrv' make: *** [all] Error 2 * ERROR: app-emulation/virtualbox-modules-4.2.16::gentoo failed (compile phase): * emake failed * * If you need support, post the output of `emerge --info '=app-emulation/virtualbox-modules-4.2.16::gentoo'`, * the complete build log and the output of `emerge -pqv '=app-emulation/virtualbox-modules-4.2.16::gentoo'`. * The complete build log is located at '/tmp/portage/app-emulation:virtualbox-modules-4.2.16:20130729-102954.log'. * For convenience, a symlink to the build log is located at '/tmp/tmerge/portage/app-emulation/virtualbox-modules-4.2.16/temp/build.log'. * The ebuild environment file is located at '/tmp/tmerge/portage/app-emulation/virtualbox-modules-4.2.16/temp/environment'. * Working directory: '/tmp/tmerge/portage/app-emulation/virtualbox-modules-4.2.16/work' * S: '/tmp/tmerge/portage/app-emulation/virtualbox-modules-4.2.16/work' >>> Failed to emerge app-emulation/virtualbox-modules-4.2.16, Log file: >>> '/tmp/portage/app-emulation:virtualbox-modules-4.2.16:20130729-102954.log' * Messages for package app-emulation/virtualbox-modules-4.2.16: * ERROR: app-emulation/virtualbox-modules-4.2.16::gentoo failed (compile phase): * emake failed * * If you need support, post the output of `emerge --info '=app-emulation/virtualbox-modules-4.2.16::gentoo'`, * the complete build log and the output of `emerge -pqv '=app-emulation/virtualbox-modules-4.2.16::gentoo'`. * The complete build log is located at '/tmp/portage/app-emulation:virtualbox-modules-4.2.16:20130729-102954.log'. * For convenience, a symlink to the build log is located at '/tmp/tmerge/portage/app-emulation/virtualbox-modules-4.2.16/temp/build.log'. * The ebuild environment file is located at '/tmp/tmerge/portage/app-emulation/virtualbox-modules-4.2.16/temp/environment'. * Working directory: '/tmp/tmerge/portage/app-emulation/virtualbox-modules-4.2.16/work' * S: '/tmp/tmerge/portage/app-emulation/virtualbox-modules-4.2.16/work' * * The following package has failed to build or install: * * (app-emulation/virtualbox-modules-4.2.16::gentoo, ebuild scheduled for merge), Log file: * '/tmp/portage/app-emulation:virtualbox-modules-4.2.16:20130729-102954.log' * Reproducible: Always
I'm afraid I cannot reproduce the problem. Can you please - try again with MAKEOPTS set to -j1 - In case the above fails as well provide the full build.log file of that compile run. - Provide "emerge --info" as well
Oh right... where does your /usr/src/linux symlink point to it it's set?
thanks for the quick help - i found the error i set chmod go-rwx /usr/src and then the package didn't compile why does this happen? chmod go-rx /usr/src - doesn't compile chmod go+rw /usr/src - compiles
lrwxrwxrwx 1 root root 12 29. Jul 12:06 /usr/src/linux -> linux-3.10.4 drwxr-xr-x 24 root root 4096 29. Jul 12:24 /usr/src/linux-3.10.4
(In reply to puchu from comment #4) > lrwxrwxrwx 1 root root 12 29. Jul 12:06 /usr/src/linux -> linux-3.10.4 > > drwxr-xr-x 24 root root 4096 29. Jul 12:24 /usr/src/linux-3.10.4 Any chance you set FEATURES="userpriv" in your make.conf file? That would make portage compile all packages as portage:portage user/group and would of course fail if /usr/src/linux-3.10.4 belongs root:root and others don't have persmission to chdir/write into that directory.
it seems usersandbox pulls it in as it is not set directly in make.conf thanks for your help