During a routine update of world, nvidia-drivers-100.14.09 emerge died with the following error: /bin/sh: scripts/basic/fixdep: Permission denied make[4]: *** [/var/tmp/portage/x11-drivers/nvidia-drivers-100.14.09/work/NVIDIA-Linux-x86_64-100.14.09-pkg2/usr/src/nv/nv.o] Error 1 make[3]: *** [_module_/var/tmp/portage/x11-drivers/nvidia-drivers-100.14.09/work/NVIDIA-Linux-x86_64-100.14.09-pkg2/usr/src/nv] Error 2 make[2]: *** [modules] Error 2 NVIDIA: left KBUILD. nvidia.ko failed to build! make[1]: *** [module] Error 1 make: *** [module] Error 2 !!! ERROR: x11-drivers/nvidia-drivers-100.14.09 failed. Call stack: ebuild.sh, line 1638: Called dyn_compile ebuild.sh, line 985: Called qa_call 'src_compile' ebuild.sh, line 44: Called src_compile nvidia-drivers-100.14.09.ebuild, line 212: Called linux-mod_src_compile linux-mod.eclass, line 516: Called die Reproducible: Always see attaches for 'emerge --info' and build log.
Created attachment 128912 [details] emerge --info
Created attachment 128914 [details] build log
Is the partition where the temporary build resides mounted "noexec" by chance?
If that's not the case, retry with FEATURES=-usersandbox
(In reply to comment #4) > If that's not the case, > retry with FEATURES=-usersandbox the filesystem allows exec and turning usersandbox off doesn't help. strangely enough, i also have an x86 machine with a similar setup, and there it compiles just fine.
You've been messing up with default umask, haven't you? :P
(In reply to comment #6) > You've been messing up with default umask, haven't you? :P haar ~ # umask 0022 is this messing???
Well, either the permissions of /usr/src/linux are messed up, or your kernel isn't configured. None of this is nvidia-drivers bug.
