if i try to build gnome-menus in a chroot, it will fail because i dont have any kernel sources. this is crazy because the only thing the ebuild does is: if use kernel_linux ; then CONFIG_CHECK="~INOTIFY" linux-info_pkg_setup fi if CONFIG_CHECK is only full of warnings, then the linux-info eclass should just continue on its way (after issuing a warning) instead of calling die
Are you sure you have the latest eclass? there is already logic for the behaviour you are requesting
looks to me like it's still broken: # head -n3 /usr/portage/eclass/linux-info.eclass # Copyright 1999-2006 Gentoo Foundation # Distributed under the terms of the GNU General Public License v2 # $Header: /var/cvsroot/gentoo-x86/eclass/linux-info.eclass,v 1.55 2008/03/21 11:11:27 dsd Exp $ # emerge gnome-menus Calculating dependencies... done! >>> Emerging (1 of 1) gnome-base/gnome-menus-2.20.3 to / * gnome-menus-2.20.3.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking gnome-menus-2.20.3.tar.bz2 ;-) ... [ ok ] * Determining the location of the kernel source code * Unable to find kernel sources at /usr/src/linux * This package requires Linux sources. * Please make sure that /usr/src/linux points at your running kernel, * (or the kernel you wish to build against). * Alternatively, set the KERNEL_DIR environment variable to the kernel sources location * * ERROR: gnome-base/gnome-menus-2.20.3 failed. * Call stack: * ebuild.sh, line 49: Called pkg_setup * gnome-menus-2.20.3.ebuild, line 30: Called linux-info_pkg_setup * linux-info.eclass, line 595: Called die * The specific snippet of code: * get_version || die "Unable to calculate Linux Kernel version" * The die message: * Unable to calculate Linux Kernel version * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/gnome-base/gnome-menus-2.20.3/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/gnome-base/gnome-menus-2.20.3/temp/die.env'.
Will be fully solved shortly, tracking in bug 283320. *** This bug has been marked as a duplicate of bug 283320 ***
