Andrew Perrin <[email protected]> writes: > Compiling modules doesn't work, whether through DKMS or using m-a:
> checking for linux kernel module build works... no > configure: error: in `/usr/src/modules/openafs': > configure: error: Fix problem or use --disable-kernel-module... > See `config.log' for more details. > I *do* have the headers installed, and have tried using the > --with-linux-kernel-headers option to configure with no luck. You don't have complete Linux kernel build system available. You're missing key files. See the error messages from config.log: > /data0/src/linux-headers-2.6.32-trunk-common/Makefile:274: > /data0/src/linux-headers-2.6.32-trunk-common/scripts/Kbuild.include: No such > file or directory > /bin/bash: > /data0/src/linux-headers-2.6.32-trunk-common/scripts/gcc-x86_64-has-stack-protector.sh: > No such file or directory > /data0/src/linux-headers-2.6.32-trunk-common/arch/x86/Makefile:81: stack > protector enabled but no compiler support You need to locate whatever package has the above-referenced files in it and make sure that the symlinks in the Linux headers tree point to them, since the kernel build system needs those files to be available to work. Normally, the scripts directory is a symlink like: lrwxrwxrwx 1 root root 30 2010-01-22 10:54 scripts -> ../linux-kbuild-2.6.32/scripts/ where in turn the linux-kbuild directory is a symlink: lrwxrwxrwx 1 root root 26 2010-01-22 10:54 linux-kbuild-2.6.32 -> ../lib/linux-kbuild-2.6.32/ Note that the links made by the Debian packages are relative by default, so if you've moved trees of files around, you may have inadvertantly broken one of these links. -- Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
