Created attachment 310807 [details] patch for nvidia-drivers-295.40.ebuild.patch (should be renamed to -r1 though) Linux removed most ${arch}/asm/system.h, dismantling them into separate files. In file included from /tmp/portage/x11-drivers/nvidia-drivers-295.40/work/kernel/nv.c:13:0: /tmp/portage/x11-drivers/nvidia-drivers-295.40/work/kernel/nv-linux.h:114:75: fatal error: asm/system.h: No such file or directoryIn file included from /tmp/portage/x11-drivers/nvidia-drivers-295.40/work/kernel/nv-chrdev.c:15:0: /tmp/portage/x11-drivers/nvidia-drivers-295.40/work/kernel/nv-linux.h:114:75: fatal error: asm/system.h: No such file or directory compilation terminated. compilation terminated. make[3]: *** [/tmp/portage/x11-drivers/nvidia-drivers-295.40/work/kernel/nv-chrdev.o] Error 1 make[3]: *** Waiting for unfinished jobs.... make[3]: *** [/tmp/portage/x11-drivers/nvidia-drivers-295.40/work/kernel/nv.o] Error 1 In file included from /tmp/portage/x11-drivers/nvidia-drivers-295.40/work/kernel/nv-acpi.c:15:0: /tmp/portage/x11-drivers/nvidia-drivers-295.40/work/kernel/nv-linux.h:114:75: fatal error: asm/system.h: No such file or directory compilation terminated. make[3]: *** [/tmp/portage/x11-drivers/nvidia-drivers-295.40/work/kernel/nv-acpi.o] Error 1 In file included from /tmp/portage/x11-drivers/nvidia-drivers-295.40/work/kernel/nv-cray.c:15:0: /tmp/portage/x11-drivers/nvidia-drivers-295.40/work/kernel/nv-linux.h:114:75: fatal error: asm/system.h: No such file or directory compilation terminated.
Created attachment 310809 [details, diff] Linux 3.4.0+ friendly patch x11-drivers/nvidia-drivers/files/linux-3.4.0.patch
Created attachment 310811 [details] full build log
You mean a kernel that's not released yet and we don't support, I'm not surprised.
Well, it isn't going to change, the merge window is closed and it'll be live in 3-4 weeks, so we might as well deal with it. If it's not fixed when it releases, I'll reopen
And it'll be re-closed. Our policy is to wait for officially supported releases and to not patch them.
*** Bug 415245 has been marked as a duplicate of this bug. ***
*** Bug 416351 has been marked as a duplicate of this bug. ***
Newest version 295.53 builds fine with 3.4-rc7. http://www.nvidia.com/object/linux-display-amd64-295.53-driver.html "Higher" but older 302.07 has the same problem.
So exactly why do you want to wait until it's released to fix this when the merge window is long sinse closed for 3.4.0, which is at rc7 and will release any day now? You could have just comitted this instead of having to continually close new dupes.
It's been the policy for years and years to not patch nvidia-drivers but wait for a new official release. It's not going to magically change. I volunteer my time to maintain Gentoo ebuilds, I do not work for you. Don't change ticket statuses either. Unfortunately a new release from nvidia came out while I am on vacation and looking at this bug on my iPad. If you need such immediate support I recommend you use a distro that has paired support with known timelines of when they will resolve your issue. If you are set on Gentoo then I recommend you hire a Gentoo developer to work in house for you. They can help maintain release candidate kernels as well as any other components those rc kernels might need (e.g. udev). Now if you don't fall into either of these categories and it's just that your compiler is idle and you see new versions on freshmeat/freecode then I'll again remind you that you are benefiting from a product put together by volunteers and not your employees. Best way to improve that product is to volunteer yourself.
*** Bug 416953 has been marked as a duplicate of this bug. ***
FYI, the supplied patch works fine here with the final 3.4 kernel and nvidia-295.49.
Use 295.53
(In reply to comment #10) > It's been the policy for years and years to not patch nvidia-drivers but > wait for a new official release. It's not going to magically change. I > volunteer my time to maintain Gentoo ebuilds, I do not work for you. Don't > change ticket statuses either. The good thing is, that you get help from the community. And this is far away from the usual complaints about nvidia drivers not compiling. This bug actually contains a very non-intrusive patch to fix nvidia-drivers. Here's a proposal: why don't you allow for patches in /etc/portage/patches? As far as I'm aware, only gcc ebuilds support custom patches in /etc/portage/patches. If nvidia-drivers would support it, much less people will probably bother you to modify the in-tree ebuilds.
*** Bug 416997 has been marked as a duplicate of this bug. ***
(In reply to comment #14) > Here's a proposal: > why don't you allow for patches in /etc/portage/patches? As far as I'm > aware, only gcc ebuilds support custom patches in /etc/portage/patches. If > nvidia-drivers would support it, much less people will probably bother you > to modify the in-tree ebuilds. As long as the patches work with epatch_user, you should be set.
*** Bug 417141 has been marked as a duplicate of this bug. ***
*** Bug 419775 has been marked as a duplicate of this bug. ***
