I'm having a problem (described in the original post, but I'll repeat it below) compiling the nvidia modules for kernel 2.6.0 using make-kpkg. I'm beginning to think the problem lies with make-kpkg. so here we go:
-running sid on an amd athlon with a self-rolled 2.4.21 kernel. -official source code downloaded and untarred in /usr/src/linux-2.6.0 -a couple of patches & things from (http://home.comcast.net/~andrex/nvidia-2.6-Debian/) downloaded and installed. Then I run: make-kpkg clean && make-kpkg --append-to-version=-nondebian1 kernel-image (as usual) No show-stopping errors there. Follwed by: make-kpkg --append-to-version=-nondebian1 modules-image or IGNORE_CC_MISMATCH=1 make-kpkg --append-to-version=-nondebian1 modules-image which gives the following response: > You appear to be compiling the NVIDIA kernel module with > a compiler different from the one that was used to compile > the running kernel. We are going to use the compiler that > were used to build the kernel with the specified headers. > (if specified in KSRC/include/linux/compile.h) > Using compiler gcc > touch /usr/src/modules/nvidia-kernel/nv/gcc-check > IGNORE_CC_MISMATCH=1 CC=gcc /usr/bin/make -C > /usr/src/modules/nvidia-kernel/nv > SYSINCLUDE=/usr/src/linux-2.6.0/include module > cat: /lib/modules/2.4.18-586-demudi/build/Makefile: No such file or > directory > cat: /lib/modules/2.4.18-586-demudi/build/Makefile: No such file or > directory > cat: /lib/modules/2.4.18-586-demudi/build/Makefile: No such file or > directory > make[2]: Entering directory `/usr/src/modules/nvidia-kernel/nv' > make: *** /lib/modules/2.4.18-586-demudi/build: No such file or > directory. Stop. > make: Entering an unknown directorymake: Leaving an unknown > directorynvidia.ko failed to build! > make[2]: *** [module] Error 1 > make[2]: Leaving directory `/usr/src/modules/nvidia-kernel/nv' > make[1]: *** [build-stamp] Error 2 > make[1]: Leaving directory `/usr/src/modules/nvidia-kernel' > Module /usr/src/modules/nvidia-kernel failed. Two wierd things here: -first, make-kpkg doesn't seem to understand that I've set IGNORE_CCMISMATCH myself. Am I not passing the variable along properly? -second, why does make-kpkg want to access module files from the running kernel? THis does not, for instance, happen when I try the non-debian method for compiling these sources mentioned in http://www.minion.de/nvidia.html (but since I don't understand how the prcess outlined there works, I'd rather stick to the tried-and-true debian way. can anyone shed light on why make-kpkg does this? thanks, matt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
