Created attachment 358472 [details] compile log for nvidia-drivers, note failed grep commads While doing an emerge -u world, nvidia-drivers-319.49 failed to compile. Testing with various kernels (3.5.7 and 3.8.13), nvidia-drivers releases (313.30, 319.49 and 325.15) showed that none of them would compile. The reason is always the same: during compile phase, the kernel version cannot be identified During the world update, portage was updated from 2.1.11.62 to 2.2.1. Downgrading portage to 2.1.12.2 immediately fixed the problem; nvidia-drivers compile runs through I am including a compile log for nvidia-drivers. There are two grep entries, which fail due to a permission conflict on '/usr/src/linux/.config'. As this file is not readable to non-root users, I suspect that some sub-process of 'emerge nvidia-drivers' is not running with root privileges (conftest.sh in the src/kernel subdirector) when started by a portage 2.2.* emerge. This will very probably cause the failure
FEATURES="userpriv" is now on by default, and your permissions in /usr/src/linux are broken. Regular users should have read permissions in /usr/src/linux.
The privileges in/usr/sr/linux are secondary. The main question is: when I start an 'emerge nvidia-drivers' as root, why does any sub-process of the emerge run as non-root ? I do not agree that regular users should have full read access to /usr/src/linux as some of the kernel settings are security relevant and should not be public on a multi-user system
FEATURES="userpriv" is what makes emerge run as non-root. Disable this in make.conf (FEATURES="-userpriv") if you'd like to go back to the old behavior.
