using a 2.4 kernel on emerging sys-fs/fuse I get: * Found kernel source directory: * /usr/src/linux * Found kernel object directory: * /lib/modules/2.4.32-gentoo-r7/build * Found sources for kernel version: * 2.4.32-gentoo-r7 * Checking for suitable kernel configuration options... [ ok ] >>> Unpacking source... >>> Unpacking fuse-2.6.1.tar.gz to /var/tmp/portage/fuse-2.6.1/work ... ... * Preparing fuse module * econf: updating fuse-2.6.1/config.guess with /usr/share/gnuconfig/config.guess * econf: updating fuse-2.6.1/config.sub with /usr/share/gnuconfig/config.sub ./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --with-kernel=/usr/src/linux --with-kernel-build=/lib/modules/2.4.32-gentoo-r7/build --libdir=/usr/lib --build=i686-pc-linux-gnu checking for a BSD-compatible install... /bin/install -c checking kernel source directory... /usr/src/linux checking kernel build directory... /lib/modules/2.4.32-gentoo-r7/build checking kernel source version... 2.4.32-gentoo-r7 configure: NOTE: Disabled building the kernel module, because this release only NOTE: supports Linux versions 2.6.9 or later. You can use the kernel NOTE: module from an earlier FUSE release with the library from this NOTE: release. configure: creating ./config.status config.status: creating Makefile config.status: creating config.h ... ... make[1]: Leaving directory `/var/tmp/portage/fuse-2.6.1/work/fuse-2.6.1' dodoc: README-2.4 does not exist * Installing fuse module install: cannot stat `fuse.o': No such file or directory !!! ERROR: sys-fs/fuse-2.6.1 failed. Call stack: ebuild.sh, line 1546: Called dyn_install ebuild.sh, line 1020: Called src_install fuse-2.6.1.ebuild, line 61: Called linux-mod_src_install linux-mod.eclass, line 540: Called die !!! doins fuse.o failed !!! If you need support, post the topmost build error, and the call stack if relevant. Looks like something that should be handled by the ebuild maintainers - maybe by splitting up kernel module and library somehow that should be done because some packages depend on the new fuse library but at least put some 2.4 compatible (pre 2.6.0) fuse package back in portage, they had all been cycled out! Reproducible: Always Steps to Reproduce: 1. emerge sys-fs/fuse on kernel 2.4
Seriously; upgrade your kernel. Noone maintains 2.4 any more.
1. I have spoken to the guys in #gentoo-kernel about this prior to filing the bug. 2.4 is currently low-maintained, but kernel maintainers are being searched and even found, they expect 2.4 to stay supported at least for a while. 2. I cannot upgrade the kernel, because there are no 2.6 drivers for some of my hardware (and the 2.4 drivers aint open source so I cant port them) 3. This issue has to be handled within the ebuild and not within the kernel. Since just an older driver will have to be used together with the latest library - as the fuse source even states during configure phase - so its not even an upstream issue, just a simple ebuild problem that could probably be fixed easily by the fuse ebuild maintainers (and wether there are many maintainers for gentoo-sources-2.4.* is practically irrelevant)
you can get the old fuse ebuilds from viewcvs: http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-fs/fuse/?hideattic=0 Please accept that it would be too ugly and not following our remove ebuilds logic to provide such a thing. YOu can just keep an old ebuild in your overlay. Sorry again & I hope you will get a new driver for your hardware
It's acceptable for external kernel module maintainers to restrict their ebuilds to certain kernel versions -- external kernel modules are a living nightmare anyway, never mind trying to support a range of kernel trees with them. However, such lack of support should be documented at the ebuild level. Stefan, please modify the ebuild to bail out with eerror on 2.4, or at the very least a really noticable set of ewarns.
