This bug is being reported because this ebuild is currently trying to build against the kernel tree by accessing it through /lib/modules/`uname -r` instead than through /usr/src/linux like it should. This is bad in many situations, like: - livecd installs: the running kernel is the one from the livecd and is most likely not the same the user is installing to; - livecd chroot fixes: as above; - generic chroot: running kernel comes from outside, as above; - kernel updates: users most likely would want their system to have all the modules ready _before_ restarting. Please fix your ebuild to use /usr/src/linux. Thanks, Diego
Created attachment 174645 [details] Build log
Created attachment 193560 [details, diff] sed Makefile to not use `uname -r` I modified the ebuild to EAPI=2 and added, to src_prepare: sed -i "s:\$(UNAME):${KV_FULL}:g" ${S}/Makefile || die "sed failed"
*** Bug 239612 has been marked as a duplicate of this bug. ***
I do get at a chroot tindeebox image : --- Invalid atom in /etc/portage/package.mask/unstable: <=sci-misc/gt-itm >>> Verifying ebuild manifests >>> Emerging (1 of 1) app-misc/usbirboy-0.3.1-r1 >>> Failed to emerge app-misc/usbirboy-0.3.1-r1, Log file: >>> '/var/log/portage/app-misc:usbirboy-0.3.1-r1:20150226-100955.log' * Package: app-misc/usbirboy-0.3.1-r1 * Repository: gentoo * Maintainer: media-tv@gentoo.org * USE: abi_x86_64 amd64 elibc_glibc kernel_linux userland_GNU * FEATURES: preserve-libs sandbox userpriv usersandbox * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found sources for kernel version: * 3.19.0-gentoo ln: failed to create symbolic link ‘Module.symvers’: File exists * Preparing usbirboy module Makefile:30: *** recipe commences before first target. Stop. emake failed and wonder how to avoid such an error ?
*** This bug has been marked as a duplicate of bug 250301 ***
