error message is: checking kernel source version... Not found configure: error: *** Cannot find UTS_RELEASE definition. !!! Please attach the following file when seeking support: !!! /var/tmp/portage/sys-kernel/spl-9999/work/spl-9999/config.log * ERROR: sys-kernel/spl-9999::gentoo failed (configure phase): * econf failed * * Call stack: * ebuild.sh, line 93: Called src_configure * environment, line 5340: Called autotools-utils_src_configure * environment, line 942: Called econf '--docdir=/usr/share/doc/spl-9999' '--bindir=/bin' '--sbindir=/sbin' '--with-config=all' '--with-linux=/usr/src/linux' '--with-linux-obj=/lib/modules/3.10.0_plus-ck1/build' '--disable-debug' '--disable-debug-log' * phase-helpers.sh, line 577: Called die * The specific snippet of code: * die "econf failed" * * If you need support, post the output of `emerge --info '=sys-kernel/spl-9999::gentoo'`, * the complete build log and the output of `emerge -pqv '=sys-kernel/spl-9999::gentoo'`. * The complete build log is located at '/var/log/portage/sys-kernel:spl-9999:20130913-224810.log'. * For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-kernel/spl-9999/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-kernel/spl-9999/temp/environment'. * Working directory: '/var/tmp/portage/sys-kernel/spl-9999/work/spl-9999' * S: '/var/tmp/portage/sys-kernel/spl-9999/work/spl-9999' >>> Failed to emerge sys-kernel/spl-9999, Log file: >>> '/var/log/portage/sys-kernel:spl-9999:20130913-224810.log' *** Resuming merge... >>> Emerging (1 of 2) sys-fs/zfs-kmod-9999 * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux ^C Exiting on signal 2 * Messages for package sys-kernel/spl-9999: * ERROR: sys-kernel/spl-9999::gentoo failed (configure phase): * econf failed * * Call stack: * ebuild.sh, line 93: Called src_configure * environment, line 5340: Called autotools-utils_src_configure * environment, line 942: Called econf '--docdir=/usr/share/doc/spl-9999' '--bindir=/bin' '--sbindir=/sbin' '--with-config=all' '--with-linux=/usr/src/linux' '--with-linux-obj=/lib/modules/3.10.0_plus-ck1/build' '--disable-debug' '--disable-debug-log' * phase-helpers.sh, line 577: Called die * The specific snippet of code: * die "econf failed" * * If you need support, post the output of `emerge --info '=sys-kernel/spl-9999::gentoo'`, * the complete build log and the output of `emerge -pqv '=sys-kernel/spl-9999::gentoo'`. * The complete build log is located at '/var/log/portage/sys-kernel:spl-9999:20130913-224810.log'. * For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-kernel/spl-9999/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-kernel/spl-9999/temp/environment'. * Working directory: '/var/tmp/portage/sys-kernel/spl-9999/work/spl-9999' * S: '/var/tmp/portage/sys-kernel/spl-9999/work/spl-9999' config.log: http://pastebin.com/j2ymnkhV install/search for the sources works with portage-2.2.0_alpha179 and portage-2.2.0_alpha185 (those are portage-releases that I made backups of after install) didn't have a chance to test 2.2.0 but at least with 2.2.1 it fails I tried installing it against compiled vanilla sources, clean compile, added uts-release header stuff, modified/fixed permissions and other things but no change
current tested portage-version was 2.2.4 where it also failed/fails
(In reply to Matt from comment #0) > config.log: > > http://pastebin.com/j2ymnkhV Please attach that file to this bug report.
Created attachment 358648 [details] sys-kernel/spl-9999/work/spl-9999/config.log config.log from sys-kernel/spl-9999 with the error message of emerge attempt with sys-apps/portage-2.2.4
Created attachment 358724 [details] /var/tmp/portage/app-emulation/virtualbox-modules-4.2.18/temp/build.log issue also happens with app-emulation/virtualbox-modules-4.2.16 and 4.2.18 with portage 2.2.1 & 2.2.4: >>> Verifying ebuild manifests >>> Emerging (1 of 1) app-emulation/virtualbox-modules-4.2.18 * vbox-kernel-module-src-4.2.18.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.11.0_plus-ck1/build * Found sources for kernel version: * 3.11.0_plus-ck1 >>> Unpacking source... >>> Unpacking vbox-kernel-module-src-4.2.18.tar.xz to /var/tmp/portage/app-emulation/virtualbox-modules-4.2.18/work >>> Source unpacked in /var/tmp/portage/app-emulation/virtualbox-modules-4.2.18/work >>> Preparing source in /var/tmp/portage/app-emulation/virtualbox-modules-4.2.18/work ... >>> Source prepared. >>> Configuring source in /var/tmp/portage/app-emulation/virtualbox-modules-4.2.18/work ... >>> Source configured. >>> Compiling source in /var/tmp/portage/app-emulation/virtualbox-modules-4.2.18/work ... ln: failed to create symbolic link ‘Module.symvers’: File exists * Preparing vboxdrv module make -j9 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.11.0_plus-ck1/build all *** Building 'vboxdrv' module *** make[1]: Entering directory `/var/tmp/portage/app-emulation/virtualbox-modules-4.2.18/work/vboxdrv' Makefile:199: *** Error: unable to find the include directory for your current Linux kernel. Specify KERN_INCL=<directory> and run Make again. Stop. make[1]: Leaving directory `/var/tmp/portage/app-emulation/virtualbox-modules-4.2.18/work/vboxdrv' make: *** [all] Error 2 * ERROR: app-emulation/virtualbox-modules-4.2.18::gentoo failed (compile phase): * emake failed * * If you need support, post the output of `emerge --info '=app-emulation/virtualbox-modules-4.2.18::gentoo'`, * the complete build log and the output of `emerge -pqv '=app-emulation/virtualbox-modules-4.2.18::gentoo'`. * The complete build log is located at '/var/log/portage/app-emulation:virtualbox-modules-4.2.18:20130915-161550.log'. * For convenience, a symlink to the build log is located at '/var/tmp/portage/app-emulation/virtualbox-modules-4.2.18/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-emulation/virtualbox-modules-4.2.18/temp/environment'. * Working directory: '/var/tmp/portage/app-emulation/virtualbox-modules-4.2.18/work' * S: '/var/tmp/portage/app-emulation/virtualbox-modules-4.2.18/work' >>> Failed to emerge app-emulation/virtualbox-modules-4.2.18, Log file: >>> '/var/log/portage/app-emulation:virtualbox-modules-4.2.18:20130915-161550.log' * Messages for package app-emulation/virtualbox-modules-4.2.18: * ERROR: app-emulation/virtualbox-modules-4.2.18::gentoo failed (compile phase): * emake failed * * If you need support, post the output of `emerge --info '=app-emulation/virtualbox-modules-4.2.18::gentoo'`, * the complete build log and the output of `emerge -pqv '=app-emulation/virtualbox-modules-4.2.18::gentoo'`. * The complete build log is located at '/var/log/portage/app-emulation:virtualbox-modules-4.2.18:20130915-161550.log'. * For convenience, a symlink to the build log is located at '/var/tmp/portage/app-emulation/virtualbox-modules-4.2.18/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-emulation/virtualbox-modules-4.2.18/temp/environment'. * Working directory: '/var/tmp/portage/app-emulation/virtualbox-modules-4.2.18/work' * S: '/var/tmp/portage/app-emulation/virtualbox-modules-4.2.18/work' * * The following package has failed to build or install: * * (app-emulation/virtualbox-modules-4.2.18::gentoo, ebuild scheduled for merge), Log file: * '/var/log/portage/app-emulation:virtualbox-modules-4.2.18:20130915-161550.log' * as mentioned above, with portage-2.2.0_alpha185 it works/compiles fine (applies to virtualbox-modules and sys-kernel/spl both 9999 and 0.6.2)
Experienced the same Problem. In my case, it helped to compile the kernel before emerging sys-kernel/spl.
(In reply to Urs Zurbuchen from comment #5) > Experienced the same Problem. In my case, it helped to compile the kernel > before emerging sys-kernel/spl. then it's not really the same issue for you :) getting that message when the kernel source has not been compiled as far as I know has been posted numerous times on the forums, etc. an for that case compiling source is the solution for me the kernel is up and running (and of course it's compiled) if I remember correctly I tried it besides on my properly compiled kernel sources directory - also just for fun to compile it via the identical kernel config & make && make modules (the kernel uses genkernel for more convenience in using lvm & cryptsetup)
*bump* any way to test later 2.2.0 alpha versions of portage to pinpoint the version in which this got introduced ? when trying to build the manifest & fetching/emerging the portage-versions from http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-apps/portage/?hideattic=0 the patch can't be found anymore
ok, worked it out via chmod -R go+rX no idea why that command showed no effect on the previous attempts :/
