The lufs-0.9.7-r1 prints out the following output when trying to emerge it. The bad thing about is that I have used the "config-kernel --output-dir default". Please, ask me further because I'm quite confused with the koutput stuff now but I've tried IMO all possible combinations... Radek sol sys-kernel # emerge sys-fs/lufs Calculating dependencies ...done! >>> emerge (1 of 1) sys-fs/lufs-0.9.7-r1 to / >>> md5 src_uri ;-) lufs-0.9.7.tar.gz >>> Unpacking source... * /usr/src/linux is a symbolic link * Determining the real directory of the Linux kernel source code * Building for Linux 2.6.5-gentoo-r1 found in /usr/src/linux * which outputs to /var/tmp/kernel-output/2.6.5-gentoo-r1 >>> Unpacking lufs-0.9.7.tar.gz to /var/tmp/portage/lufs-0.9.7-r1/work * Applying lufs-0.9.7-fPIC.patch... [ ok ] * Applying gentoo-gcc332fix-0.9.7.patch... [ ok ] >>> Source unpacked. * Due to the 2.6 kernel build system, external module compilation * with a normal setup requires write access to //usr/src/linux * There are several ways to fix/prevent this. * Users can willingly let portage make this writable by doing * # config-kernel --allow-writable yes * However, this is considered a security risk! * * The prefered method is to enable Gentoo's new 'koutput' method * for kernel modules. See the doc * http://www.gentoo.org/doc/en/2.6-koutput-user.xml * To enable this, you'll need to run * # config-kernel --output-dir /var/tmp/kernel-output * and then install a new kernel !!! ERROR: sys-fs/lufs-0.9.7-r1 failed. !!! Function kmod_make_linux_writable, Line 207, Exitcode 0 !!! Incompatible kernel setup
I followed the instructions available from http://www.gentoo.org/doc/en/2.6-koutput-user.xml to the letter and got past the error you're having but I get another error: kernel headers not found.
koutput is depreciated and no longer used maintained. This is because of the build system fixes that the kernel developers commited to the 2.6.6 kernel. As as result, it is no longer supported by Gentoo Mobile team. Below is the post to gentoo-dev mailing list by the creator of the koutput system. Hey all, Been busy with lots of other things, and dreading sending this anyway, but I wanted to clear things up Re: the koutput/kbuild stuff that I'd worked on to fix some problems previously related to 2.6 kernel build issues. Unfortunately, the fix that was 95% implemented, and had the beginnings of code in the tree got ham-strung by a combination of kernel stuff changing under my/our feet, and Real Life (tm) things coming in at just the wrong time. As a result, the kmod.eclass, and config-kernel have several problems, and are only 1/2 implemented anyway. Sooo, don't use kmod.eclass. Just don't. config-kernel i will be package.masking as well soon. I know there are a few ebuilds out there that currently use kmod.eclass for a few things. I'll be contacting those maintainers over the next few days to address things with them, and get them sorted out with how to get things working with 2.6.6 and newer kernels. If you get any bugs from people complaining about such and such ebuild not working with koutput, assing or CC me, and i'll deal with it. Thanks. Sorry for any confusion folks. -pete
