Here is the message output from the emerge: * QA Notice: The following files contain executable stacks * Files with executable stacks will not work properly (or at all!) * on some architectures/operating systems. A bug should be filed * at http://bugs.gentoo.org/ to make sure the file is fixed. * For more information, see http://hardened.gentoo.org/gnu-stack.xml * Please include the following list of files in your report: * !WX --- --- usr/lib64/libXvMCNVIDIA.a:NVXVMC.o Reproducible: Always Steps to Reproduce: 1. emerge =x11-drivers/nvidia-drivers-177.82 I really don't know much about this, but let me know if there's anything else I can provide.
I have the same problem with 173.14.15 on amd64 and kernels 2.6.27 and 2.6.28. The thing is that the problem surfaced when I changed profile from 2007.0 to 2008.0 and it is a remerge (due to changed use flags).
nvidia-drivers are masked on our profiles for hardened. But even if they were not. Hardened is not the default dumping ground for these types of things. Reassigning to maintainers who will probably close as UPSTREAM as those are a 3rd party binary driver that we are helpless to fix.
(In reply to comment #2) > nvidia-drivers are masked on our profiles for hardened. But even if they were > not. Hardened is not the default dumping ground for these types of things. Sorry to dump it on hardened, but that was the only hint I got from the emerge output. This is what happens when I file a bug report because my software tells me to....
Version 180.22 introduces furthermore: * QA Notice: The following files contain runtime text relocations * Text relocations force the dynamic linker to perform extra * work at startup, waste system resources, and may pose a security * risk. On some architectures, the code may not even function * properly, if at all. * For more information, see http://hardened.gentoo.org/pic-fix-guide.xml * Please include the following list of files in your report: * TEXTREL usr/lib32/libvdpau_nvidia.so.180.22 I do not open a new bug report as this can probably also only be fixed upstream.
I found a work-around. Changing profile from 2008.0/desktop to plain 2008.0 solved the problem for me.
Newer ebuilds mask this warning. This will have to be fixed by NVIDIA since its in the binary pieces.