* QA Notice: The following files contain writable and executable sections * Files with such sections 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 issue is fixed. * For more information, see http://hardened.gentoo.org/gnu-stack.xml * Please include the following list of files in your report: * Note: Bugs should be filed for the respective maintainers * of the package in question and not hardened@g.o. * RWX --- RWX usr/share/qemu/openbios-sparc32 * RWX --- RWX usr/share/qemu/openbios-sparc64 * RWX --- RWX usr/share/qemu/openbios-ppc * --- --- RWX usr/bin/qemu-x86_64 * --- --- RWX usr/bin/qemu-sh4eb * --- --- RWX usr/bin/qemu-mipsel * --- --- RWX usr/bin/qemu-sparc64 * --- --- RWX usr/bin/qemu-m68k * --- --- RWX usr/bin/qemu-i386 * --- --- RWX usr/bin/qemu-armeb * --- --- RWX usr/bin/qemu-sh4 * --- --- RWX usr/bin/qemu-sparc * --- --- RWX usr/bin/qemu-alpha * --- --- RWX usr/bin/qemu-sparc32plus * --- --- RWX usr/bin/qemu-microblaze * --- --- RWX usr/bin/qemu-arm * --- --- RWX usr/bin/qemu-cris * --- --- RWX usr/bin/qemu-mips Reproducible: Always Steps to Reproduce: 1. app-emulation/qemu-kvm-0.12.5-r1 Actual Results: Warning messages pasted above near the end of the compilation are displayed. Expected Results: No warning messages should be displayed. Opening bug per emerge request (see the log).
The first three are BIOS files and cannot be touched; the others are used for JIT, I doubt there is anything we can do about them either…
Yeah I have no idea how to resolve this for JIT compilers.
* QA Notice: Pre-stripped files found: * /usr/share/qemu/openbios-ppc * /usr/share/qemu/openbios-sparc32 * /usr/share/qemu/openbios-sparc64 * QA Notice: The following files contain writable and executable sections * Files with such sections 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 issue is fixed. * For more information, see http://hardened.gentoo.org/gnu-stack.xml * Please include the following list of files in your report: * Note: Bugs should be filed for the respective maintainers * of the package in question and not hardened@g.o. * --- --- RWX usr/bin/qemu-x86_64 * --- --- RWX usr/bin/qemu-i386 * --- --- RWX usr/bin/qemu-arm * --- --- RWX usr/bin/qemu-mipsel * --- --- RWX usr/bin/qemu-mips * RWX --- RWX usr/share/qemu/openbios-ppc * RWX --- RWX usr/share/qemu/openbios-sparc32 * RWX --- RWX usr/share/qemu/openbios-sparc64 _____________________________________________________________________________ app-emulation/qemu-kvm-0.13.0-r2 Portage 2.2.0_alpha30 (hardened/linux/amd64/no-multilib, gcc-4.6.0, libc-0-r0, 2.6.38-hardened-r1 x86_64)
Fixed in newer versions that are available in the tree. Thanks for the info.
*** Bug 369571 has been marked as a duplicate of this bug. ***
Regarding the recent duplicate, this does not appear to be fully fixed in the newer version 0.14.1-r1 of qemu-kvm. Please consider the following and reopen this bug if proper. I suggest that at minimum a note should be added to the warning, stating that the user should not file a bug in case of packages dealing with virtualization, JIT or something similar. A better solution would probably be that the message about filing a bug could optionally be substituted for a better message in the ebuild. For example: QA Notice: The following files contain writable and executable sections This package makes use of virtualization/JIT techniques which require some of its binaries to have rwx sections. Files with such sections will not work properly (or at all!) on some architectures/operating systems. A bug should be filed at http://bugs.gentoo.org/ ONLY IF the binaries in this package fail to execute properly. For more information, see http://hardened.gentoo.org/gnu-stack.xml Please include the following list of files in your report: Note: Bugs should be filed for the respective maintainer Otherwise you might probably just keep receiving bug reports like this one (more waste of time for both users and Gentoo developers). Thanks for reading! :)
