Summary: | x11-drivers/nvidia-drivers-334.21 - make: *** /lib/modules/3.12.13-gentoo/build: Permission denied. Stop. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | UX.MAN <ux.man.m> |
Component: | Current packages | Assignee: | Jeroen Roovers (RETIRED) <jer> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | gentoo, nlshep, ux.man.m |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | /var/tmp/portage/x11-drivers/nvidia-drivers-334.21/temp/environment |
Description
UX.MAN
2014-03-30 04:20:12 UTC
(In reply to UX.MAN from comment #0) > * The ebuild environment file is located at > '/var/tmp/portage/x11-drivers/nvidia-drivers-334.21/temp/environment'. Please attach that file to this bug report. Created attachment 373966 [details]
/var/tmp/portage/x11-drivers/nvidia-drivers-334.21/temp/environment
Looks like a duplicate of bug #438734 or bug #434710. Ok, it looks like these bug reports you mentioned are related to this. Still, how could I resolve this issue? should I apply a patch or something? (In reply to UX.MAN from comment #4) > Ok, it looks like these bug reports you mentioned are related to this. > Still, how could I resolve this issue? should I apply a patch or something? I have no idea what is causing this in the first place. It looks like you have some variable set in the environment that's causing linux-mod.eclass or linux-info.eclass to misbehave. You tell me. Well, I don't know. I haven't set any variables like KERNEL_DIR nor KBUILD_OUTPUT. I also have the problem, and have not explicitly set any variables related to this. For me, it appeared suddenly and unrelated to any choice I directly made myself, as far as I know. The only unusual things I have set are: -PORTAGE_TMPDIR set to /tmp in make.conf -layman installed and /var/lib/layman/make.conf sourced in make.conf -using the kde/systemd profile I've wanted to debug this but haven't had enough time to dig in. If anybody has any specific tests they'd like me to run, I'd be happy to do so. I dug into this and discovered that, for me, the issue was simple file permissions. I discovered that some of the files that are created in /usr/src/linux when you compile the kernel had mode 660 due to me having a umask of 0007. This, combined with default FEATURES="userpriv", meant that necessary files were inaccessible when nvidia-drivers was compiling. This appeared for me suddenly because I had built the system I'm on and run with it a few weeks before I got around to copying over my bashrc files (which applied the umask). I'm not 100% sure this is the same problem you're having, UX.MAN, since your error message is a little different (it fails accessing /lib/modules/3.12.13-gentoo/build whereas mine failed on e.g. include/generated/uapi), but what happens if you set FEATURES="-userpriv" and try again? I think same will happen if your umask was 077 when you build kernel. |