Emerging open-vm-tools-kmod fails when KBUILD_OUTPUT is set in /etc/portage/env/app-emulation/open-vm-tools-kmod. Emerging with kernel sources configured directly in /usr/src/linux works fine. Build log: * Package: app-emulation/open-vm-tools-kmod-0.0.20110328.387002 * Repository: gentoo * Maintainer: vadimk@gentoo.org vmware@gentoo.org * USE: elibc_glibc kernel_linux userland_GNU x86 * FEATURES: sandbox userpriv usersandbox * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found kernel object directory: * /root/kernel/output * Found sources for kernel version: * 2.6.37-hardened-r7 >>> Unpacking source... >>> Unpacking open-vm-tools-2011.03.28-387002.tar.gz to /var/tmp/portage/app-emulation/open-vm-tools-kmod-0.0.20110328.387002/work >>> Source unpacked in /var/tmp/portage/app-emulation/open-vm-tools-kmod-0.0.20110328.387002/work >>> Preparing source in /var/tmp/portage/app-emulation/open-vm-tools-kmod-0.0.20110328.387002/work/open-vm-tools-2011.03.28-387002 ... >>> Source prepared. >>> Configuring source in /var/tmp/portage/app-emulation/open-vm-tools-kmod-0.0.20110328.387002/work/open-vm-tools-2011.03.28-387002 ... >>> Source configured. >>> Compiling source in /var/tmp/portage/app-emulation/open-vm-tools-kmod-0.0.20110328.387002/work/open-vm-tools-2011.03.28-387002 ... * Preparing vmblock module make HOSTCC=i686-pc-linux-gnu-gcc CROSS_COMPILE=i686-pc-linux-gnu- LDFLAGS= auto-build HEADER_DIR=/usr/src/linux/include BUILD_DIR=/root/kernel/output OVT_SOURCE_DIR=/var/tmp/portage/app-emulation/open-vm-tools-kmod-0.0.20110328.387002/work/open-vm-tools-2011.03.28-387002 Using standalone build system. Makefile:167: Makefile.normal: No such file or directory make: *** No rule to make target `Makefile.normal'. Stop. emake failed * ERROR: app-emulation/open-vm-tools-kmod-0.0.20110328.387002 failed (compile phase): * Unable to emake HOSTCC=i686-pc-linux-gnu-gcc CROSS_COMPILE=i686-pc-linux-gnu- LDFLAGS= auto-build HEADER_DIR=/usr/src/linux/include BUILD_DIR=/root/kernel/output OVT_SOURCE_DIR=/var/tmp/portage/app-emulation/open-vm-tools-kmod-0.0.20110328.387002/work/open-vm-tools-2011.03.28-387002 * * Call stack: * ebuild.sh, line 56: Called src_compile * environment, line 3384: Called linux-mod_src_compile * environment, line 2585: Called die * The specific snippet of code: * eval "emake HOSTCC=\"$(tc-getBUILD_CC)\" CROSS_COMPILE=${CHOST}- LDFLAGS=\"$(get_abi_LDFLAGS)\" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS} " || die "Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}- LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}"; * * If you need support, post the output of 'emerge --info =app-emulation/open-vm-tools-kmod-0.0.20110328.387002', * the complete build log and the output of 'emerge -pqv =app-emulation/open-vm-tools-kmod-0.0.20110328.387002'. * The complete build log is located at '/var/tmp/portage/app-emulation/open-vm-tools-kmod-0.0.20110328.387002/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-emulation/open-vm-tools-kmod-0.0.20110328.387002/temp/environment'. * S: '/var/tmp/portage/app-emulation/open-vm-tools-kmod-0.0.20110328.387002/work/open-vm-tools-2011.03.28-387002' Attachements: 1) emerge --info
Created attachment 273621 [details] Output of 'emerge --info'
I am sorry for bringing up this issue, which was caused by a misconfiguration on my part. The kernel build output was placed in a subdirectory of /root while having FEATURES="userpriv usersandbox" enabled. I did not check, whether disabling the FEATURES would fix the issue, but moving the kernel output directory to a user accessible location certainly helped.
