This is an auto-filed bug because dev-scheme/guile-json 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 640402 [details] build.log build log and emerge --info
""" * QA Notice: Files built without respecting CFLAGS have been detected * Please include the following list of files in your report: * /usr/lib64/guile/2.2/site-ccache/json/parser.go * /usr/lib64/guile/2.2/site-ccache/json/builder.go * /usr/lib64/guile/2.2/site-ccache/json.go """ These files (and any files built with guile) don't contain native code and they are not built from C sources.
(In reply to Sergei Trofimovich from comment #2) > """ > * QA Notice: Files built without respecting CFLAGS have been detected > * Please include the following list of files in your report: > * /usr/lib64/guile/2.2/site-ccache/json/parser.go > * /usr/lib64/guile/2.2/site-ccache/json/builder.go > * /usr/lib64/guile/2.2/site-ccache/json.go > """ > > These files (and any files built with guile) don't contain native code and > they are not built from C sources. if you think that the portage qa warning can be improved to bypass these situations, otherwise this is to hide the qa warning as mentioned in comment 0
That is known as a portage's bug #677600. We can workaround it all over the tree. Should we though? comment 0 mentions no bug numbers except this bug. But maybe I'm reading it wrong.
Added a workaround.
