It doesn't get very far: >>> md5 src_uri ;-) lufs-0.9.6.tar.gz >>> Unpacking source... >>> Unpacking lufs-0.9.6.tar.gz to /var/tmp/portage/lufs-0.9.6/work >>> Source unpacked. configure: WARNING: If you wanted to set the --build type, don't use --host. If a cross compiler is detected then cross compile mode will be used. checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking target system type... i686-pc-linux-gnu checking for a BSD-compatible install... /bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for i686-pc-linux-gnu-strip... no checking for strip... strip checking OS... Linux checking kernel... 2.6.0-test5-mm4 checking kernel support... configure: error: 2.6 not supported! !!! ERROR: sys-fs/lufs-0.9.6 failed. !!! Function econf, Line 324, Exitcode 1 !!! econf failed Since lufs suposedly supports 2.5 kernels, it should also support 2.6 kernels. It ought to be trivial to fix this up, and send a patch to the lufs people.
Created attachment 18851 [details, diff] patch to fix. Try this - I don't have a 2.6 kernel, so I can't test this, but it should work if the headers don't need modification.
Comment on attachment 18851 [details, diff] patch to fix. doesn't work.
OK, this is non-trivial, and I don't have enough experience of working with the kernel to fix it myself, so unless someone else wants to patch it I'd suggest marking it resolved as cantfix or later.
Created attachment 19130 [details, diff] lufs-0.9.6.Kernel2.6Support.patch --> stick in sys-fs/lufs/files/
Created attachment 19131 [details] Updated ebuild
Okay, added an updated ebuild and a patch which you stick in files. Make sure the patch is in files and has a "lufs-0.9.6.Kernel2.6Support.patch" filename! Compiles fine, but I don't know how to test this. If it works, tell me and I'll commit this in.
ftpfs seems to be working; however, I have been unable to successfully use an sshfs system.
In which case this needs upstream intervention and is not a Gentoo bug.