checking kernel source code... /usr/src/linux checking for /usr/src/linux/Makefile... yes checking for /usr/src/linux/.config... no configure: WARNING: *** kernel configuration file not found. Either this isn't a kernel tree, or it hasn't been configured. checking kernel is version 2.6.0+... configure: WARNING: *** unsupported kernel version source no configure: creating ./config.status config.status: creating Makefile config.status: creating docs/Makefile config.status: creating dpkg/Makefile config.status: creating docs/doxygen.cfg config.status: creating examples/Makefile config.status: creating kbuild/Makefile config.status: creating src/Makefile config.status: executing depfiles commands ----------------------------------------------------- configuration complete libifp: no linux kernel module: no examples: no documentation: no ----------------------------------------------------- type 'make' to build make[1]: Entering directory `/var/tmp/portage/media-sound/libifp-module-1.0.0.2/work/libifp-1.0.0.2' make[1]: Nothing to be done for `all-am'. make[1]: Leaving directory `/var/tmp/portage/media-sound/libifp-module-1.0.0.2/work/libifp-1.0.0.2' >>> Source compiled. >>> Test phase [not enabled]: media-sound/libifp-module-1.0.0.2 >>> Install libifp-module-1.0.0.2 into /var/tmp/portage/media-sound/libifp-module-1.0.0.2/image/ category media-sound * Installing libifp module install: cannot stat `libifp.ko': No such file or directory !!! ERROR: media-sound/libifp-module-1.0.0.2 failed. Call stack: ebuild.sh, line 1632: Called dyn_install ebuild.sh, line 1077: Called qa_call 'src_install' ebuild.sh, line 44: Called src_install ebuild.sh, line 1322: Called linux-mod_src_install linux-mod.eclass, line 546: Called die !!! doins libifp.ko failed My kernel configuration etc is in /usr/src/build/ # grep KBUILD /etc/make.conf KBUILD_OUTPUT="/usr/src/build" the above works perfectly for other modules such as nvidia and gspcav1, why not libifp-module which seems to be as bare bones an ebuild as it can get?
Just ran into this bug again. Still no resolution? :(
I suspect this bug might be a consequence of bug # 331467 which I have just reported.
Removed from tree per bug 286081
