This bug has been discussed a bit on nvforums, a simple google search returns a very minor patch that fixes this. I've tested it myself in a local overlay. http://notes.benv.junerules.com/linux-3-8-and-nvidia-driver/ Reproducible: Always Steps to Reproduce: 1. emerge =gentoo-sources-3.8.0 2. emerge -1 nvidia-drivers 3. get failure about warnings being treated as errors Actual Results: Failure to build Expected Results: A built kernel modules for 3.8 The error is something like this: /tmp/selfgz7139/NVIDIA-Linux-x86_64-313.18/kernel/nv.c: In function ‘nv_kern_open’: /tmp/selfgz7139/NVIDIA-Linux-x86_64-313.18/kernel/nv.c:1521:30: warning: passing argument 2 of ‘request_irq’ from incompatible pointer type [enabled by default] In file included from /tmp/selfgz7139/NVIDIA-Linux-x86_64-313.18/kernel/nv-linux.h:128:0, from /tmp/selfgz7139/NVIDIA-Linux-x86_64-313.18/kernel/nv.c:13: include/linux/interrupt.h:130:1: note: expected ‘irq_handler_t’ but argument is of type ‘enum irqreturn_t (*)(int, void *, struct pt_regs *)’ /tmp/selfgz7139/NVIDIA-Linux-x86_64-313.18/kernel/nv.c:1525:17: error: implicit declaration of function ‘NV_TASKQUEUE_INIT’ [-Werror=implicit-function-declaration] /tmp/selfgz7139/NVIDIA-Linux-x86_64-313.18/kernel/nv.c:1537:25: warning: passing argument 2 of ‘request_irq’ from incompatible pointer type [enabled by default] In file included from /tmp/selfgz7139/NVIDIA-Linux-x86_64-313.18/kernel/nv-linux.h:128:0, from /tmp/selfgz7139/NVIDIA-Linux-x86_64-313.18/kernel/nv.c:13: include/linux/interrupt.h:130:1: note: expected ‘irq_handler_t’ but argument is of type ‘enum irqreturn_t (*)(int, void *, struct pt_regs *)’ cc1: some warnings being treated as errors make[3]: *** [/tmp/selfgz7139/NVIDIA-Linux-x86_64-313.18/kernel/nv.o] Error 1 make[2]: *** [_module_/tmp/selfgz7139/NVIDIA-Linux-x86_64-313.18/kernel] Error 2 NVIDIA: left KBUILD. nvidia.ko failed to build! make[1]: *** [module] Error 1 make: *** [module] Error 2 -> Error. ERROR: Unable to build the NVIDIA kernel module.
Created attachment 339976 [details, diff] Said patch mentioned above Here is the patch to fix the issue.
*** This bug has been marked as a duplicate of bug 447566 ***