Bug 55697 – kernel module ebuilds fail even after following instructions at http://www.gentoo.org/doc/en/2.6-koutput-user.xml

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Matthew C. Mead 2004-06-30 10:38:51 UTC]

I've followed all the directions at http://www.gentoo.org/doc/en/2.6-koutput-user.xml for using an alternate KBUILD_OUTPUT directory.  When I attempt to emerge an ebuild that builds a kernel module, I get the following output:

>>> Unpacking source...
 * /usr/src/linux is a symbolic link
 * Determining the real directory of the Linux kernel source code
 * Building for Linux 2.6.7-gentoo-r6 found in /usr/src/linux
 * which outputs to /var/tmp/kernel-output/2.6.7-gentoo-r6
>>> Unpacking lufs-0.9.7.tar.gz to /var/tmp/portage/lufs-0.9.7-r2/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


Reproducible: Always
Steps to Reproduce:
1. follow instructions at http://www.gentoo.org/doc/en/2.6-koutput-user.xml
2. rebuild kernel and install
3. attempt to emerge lufs kernel module.

Actual Results:  
Same results.

Expected Results:  
Continued to build the lufs kernel module.

[Comment 1 John Mylchreest (RETIRED) 2004-11-07 08:35:08 UTC]

tjhis is quite outdated now wirth a new solution being worked on.