Attempts to build gnat-gcc bomb off with a QA Notice. Reproducible: Always Steps to Reproduce: 1. emerge --unmerge gnat 2. unset ADA_INCLUDE_PATH ADA_OBJECTS_PATH 3. ACCEPT_KEYWORDS=~x86 emerge -va gnat-gcc Actual Results: * 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 this file in your report: * /home/saves/portage/temp/portage/dev-lang/gnat-gcc-4.1.2/temp/scanelf-execstack.log * RWX --- --- usr/libexec/gnat-gcc/i686-pc-linux-gnu/4.1/gnat1 RWX --- --- usr/lib/gnat-gcc/i686-pc-linux-gnu/4.1/adalib/libgnat-4.1.so RWX --- --- usr/i686-pc-linux-gnu/gnat-gcc-bin/4.1/gnatbind RWX --- --- usr/i686-pc-linux-gnu/gnat-gcc-bin/4.1/gnatls RWX --- --- usr/i686-pc-linux-gnu/gnat-gcc-bin/4.1/gnatmake * QA Notice: // installed in ${D}/${D} * QA Notice: //usr installed in ${D}/${D} !!! ERROR: dev-lang/gnat-gcc-4.1.2 failed. Call stack: misc-functions.sh, line 570: Called install_qa_check misc-functions.sh, line 212: Called die !!! Aborting due to QA concerns: 2 files installed in /home/saves/portage/temp/portage/dev-lang/gnat-gcc-4.1.2/image///home/saves/portage/temp/portage/dev-lang/gnat-gcc-4.1.2/image/ !!! If you need support, post the topmost build error, and the call stack if relevant. !!! A complete build log is located at '/home/saves/portage/logs/dev-lang:gnat-gcc-4.1.2:20070512-025141.log'. !!! install_qa_check failed; exiting. Expected Results: Successful emerge. I will attach the file as suggested in the abort message. I left the hardware as 'all', but have actually only tried it on three x86 archictures (AMD desktop, Intel desktop, and Intel mobile). I synched and -uvaD'd world before attempting the installation. The unmerge of dev-lang/gnat did not leave anything in /etc/env.d
Created attachment 118960 [details] scanelf-execstack.log, as mentioned in the emerge abort message
Just to confirm - I see the same - with gnat-gcc-4.1.2: * QA Notice: // installed in ${D}/${D} * QA Notice: //usr installed in ${D}/${D} Interesting that on gnat-gcc, just '/' and '/usr' are installed into ${D}/${D} (i.e. nothing of any consequence) - with gnat-gpl there's a pile of stuff there.
Just added a change to gnatbuild.eclass as in #178140. Should fix this bug.
