quite recently I've noticed that the ebuilds for splashutils have all been modified to use ${KBUILD_OUTPUT} instead of ${KBUILD_OUTPUT_PREFIX} for my own system ${KBUILD_OUTPUT_PREFIX} points to /var/tmp/kernel-output also for info I've used config-kernel to relocate the kernel build directory e.g. /var/tmp/kernel-output/2.6.10-mygen-r7 I suspect that ${KBUILD_OUTPUT} should point to /var/tmp/kernel-output/<kernel version> or to /lib/modules/<kernel version>/build (which is just a symbolic link to the above) but since ${KBUILD_OUTPUT} is empty splashutils thinks there is no .config file and therefore that the kernel hasn't been configured Also instead of a new revision being created the original ebuilds have just been modified. Since I have more than one system I was able to get a copy of the old ebuild (which is okay) before running emerge sync. I've attached this above if anyone needs it Reproducible: Always Steps to Reproduce: 1. Have a kernel with a relocated build directory using config-kernel 2. emerge splashutils Actual Results: bash-2.05b# emerge splashutils Calculating dependencies ...done! >>> emerge (1 of 1) media-gfx/splashutils-0.9.1 to / >>> md5 src_uri ;-) splashutils-0.9.1.tar.bz2 >>> md5 src_uri ;-) miscsplashutils-0.1.2.tar.bz2 >>> md5 src_uri ;-) splashutils-gentoo-0.1.4.tar.bz2 >>> md5 src_uri ;-) fbsplash-theme-emergence-r2.tar.bz2 >>> md5 src_uri ;-) fbsplash-theme-gentoo-r1.tar.bz2 >>> Unpacking source... >>> Unpacking splashutils-0.9.1.tar.bz2 to /var/tmp/portage/splashutils-0.9.1/work >>> Unpacking miscsplashutils-0.1.2.tar.bz2 to /var/tmp/portage/splashutils-0.9.1/work >>> Unpacking splashutils-gentoo-0.1.4.tar.bz2 to /var/tmp/portage/splashutils-0.9.1/work >>> Unpacking fbsplash-theme-emergence-r2.tar.bz2 to /var/tmp/portage/splashutils-0.9.1/work >>> Unpacking fbsplash-theme-gentoo-r1.tar.bz2 to /var/tmp/portage/splashutils-0.9.1/work * It appears that your kernel has not been configured. Please run at least * `make prepare` before merging splashutils. !!! ERROR: media-gfx/splashutils-0.9.1 failed. !!! Function src_unpack, Line 57, Exitcode 0 !!! Kernel not configured !!! If you need support, post the topmost build error, NOT this status message. Expected Results: bash-2.05b# emerge splashutils Calculating dependencies ...done! >>> emerge (1 of 1) media-gfx/splashutils-0.9.1-r1 to / >>> md5 src_uri ;-) splashutils-0.9.1.tar.bz2 >>> md5 src_uri ;-) miscsplashutils-0.1.2.tar.bz2 >>> md5 src_uri ;-) splashutils-gentoo-0.1.4.tar.bz2 >>> md5 src_uri ;-) fbsplash-theme-emergence-r2.tar.bz2 >>> md5 src_uri ;-) fbsplash-theme-gentoo-r1.tar.bz2 >>> Unpacking source... test >>> Unpacking splashutils-0.9.1.tar.bz2 to /var/tmp/portage/splashutils-0.9.1-r1/work >>> Unpacking miscsplashutils-0.1.2.tar.bz2 to /var/tmp/portage/splashutils-0.9.1-r1/work >>> Unpacking splashutils-gentoo-0.1.4.tar.bz2 to /var/tmp/portage/splashutils-0.9.1-r1/work >>> Unpacking fbsplash-theme-emergence-r2.tar.bz2 to /var/tmp/portage/splashutils-0.9.1-r1/work >>> Unpacking fbsplash-theme-gentoo-r1.tar.bz2 to /var/tmp/portage/splashutils-0.9.1-r1/work >>> Source unpacked. MAKE klibc opening ../linux/include/linux/errno.h ... etc experiancing this bug on a amd64 system which is up to date and a P4 system that I'm in the middle of updating at the moment if there is a new package somewhere that defines KBUILD_OUTPUT (that I just haven't found / installed yet) then this should probably be added to splashutils as a depend I couldn't see KBUILD_OUTPUT being set within any of the eclasses or anywhere within /etc/env.d/ only KBUILD_OUTPUT_PREFIX within /etc/env.d/05kernel
Created attachment 53334 [details] old ebuild file splashutils-0.9.1.ebuild
I confirm the bug, as I experienced it as well. KBUILD_OUTPUT is NOT defined in my system, but KBUILD_OUTPUT_PREFIX is.
As explained in #84510, KBUILD_OUTPUT_PREFIX is deprecated and not supported anymore. Please switch to KBUILD_OUTPUT. If the variable is not defined anywhere, feel free to define them by yourself. I'm sorry for all the confusion this switch might be causing.
*** Bug 89662 has been marked as a duplicate of this bug. ***