This is an auto-filed bug because dev-scheme/guile-gcrypt 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 640396 [details] build.log build log and emerge --info
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4ebe40715db22f1494ee1b5d950e49b5240a4a62 commit 4ebe40715db22f1494ee1b5d950e49b5240a4a62 Author: Sergei Trofimovich <slyfox@gentoo.org> AuthorDate: 2020-05-22 18:15:23 +0000 Commit: Sergei Trofimovich <slyfox@gentoo.org> CommitDate: 2020-05-22 18:15:23 +0000 dev-scheme/guile-gcrypt: add QA CFLAGS workaround, bug #724070 guile does not use CFLAGS, it's a portage's false positive (see bug #677600). Reported-by: Agostino Sarubbo Closes: https://bugs.gentoo.org/724070 Bug: https://bugs.gentoo.org/677600 Package-Manager: Portage-2.3.99, Repoman-2.3.22 Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org> dev-scheme/guile-gcrypt/guile-gcrypt-0.2.1.ebuild | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)