This is an auto-filed bug because app-editors/e3 does not respect CFLAGS. The issue was originally discovered on amd64, but it may be reproducible on other arches as well. If you think that a different summary clarifies the issue better, feel free to change it. Attached build log and emerge --info. NOTE: To reproduce this issue you may want to set CFLAGS="${CFLAGS} -frecord-gcc-switches". If this is not something about c/c++ context you may want to set also FFLAGS and FCFLAGS or just see this bug as an hint to hide the QA warning where is not possible to respect CFLAGS.
Created attachment 642906 [details] build.log build log and emerge --info
e3 is written in assembly language, therefore it is being built using nasm, not gcc. Looks like a false positive to me.
It looks like a common policy is to disable the qa check on that file like is described at the end of comment 0
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a7da86e81692acfbcfc627afb45477756c45290b commit a7da86e81692acfbcfc627afb45477756c45290b Author: Ulrich Müller <ulm@gentoo.org> AuthorDate: 2020-05-31 19:57:45 +0000 Commit: Ulrich Müller <ulm@gentoo.org> CommitDate: 2020-05-31 19:58:19 +0000 app-editors/e3: Set QA_FLAGS_IGNORED for e3 binary. Suppresses false positive QA warning for CFLAGS. Closes: https://bugs.gentoo.org/726484 Package-Manager: Portage-2.3.100, Repoman-2.3.22 Signed-off-by: Ulrich Müller <ulm@gentoo.org> app-editors/e3/e3-2.8.2.ebuild | 1 + 1 file changed, 1 insertion(+)
