Summary: | www-client/chromium-25.0.1364.26 - QA Notice: Files built without respecting CFLAGS have been detected | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | iGentoo <AlphatPC> |
Component: | Current packages | Assignee: | Chromium Project <chromium> |
Status: | RESOLVED FIXED | ||
Severity: | QA | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | chromium-25.0.1364.26-build.log.tar.xz |
Description
iGentoo
2013-01-14 18:22:56 UTC
Created attachment 335634 [details]
chromium-25.0.1364.26-build.log.tar.xz
Please do not CC maintainers when you cannot assign bugs. (In reply to comment #0) > * QA Notice: Files built without respecting CFLAGS have been detected > * Please include the following list of files in your report: > * /usr/lib64/chromium-browser/nacl_irt_srpc_x86_64.nexe > * /usr/lib64/chromium-browser/nacl_irt_x86_64.nexe > * /usr/lib64/chromium-browser/nacl_irt_x86_32.nexe > * /usr/lib64/chromium-browser/nacl_irt_srpc_x86_32.nexe > > set QA_FLAGS_IGNORED="usr/lib[^/]*/chromium-browser[^/]*/nacl_irt_.*\.nexe" > can hide the QA notice. How can I reproduce the above message? Is it controlled by some FEATURE or something else? (In reply to comment #3) > How can I reproduce the above message? Is it controlled by some FEATURE or > something else? From make.conf.example: # If your gcc supports it, you can add -frecord-gcc-switches to all of the # following *FLAGS in order to enable *FLAGS ignorance checking for ebuilds: # CFLAGS, CXXFLAGS, FFLAGS, and FCFLAGS. # Note that this check is only enabled if every one of these variables contains # -frecord-gcc-switches, since otherwise the check could result in false # positive results. (In reply to comment #4) > From make.conf.example: > > # If your gcc supports it, you can add -frecord-gcc-switches to all of the > # following *FLAGS in order to enable *FLAGS ignorance checking for ebuilds: > # CFLAGS, CXXFLAGS, FFLAGS, and FCFLAGS. > # Note that this check is only enabled if every one of these variables > contains > # -frecord-gcc-switches, since otherwise the check could result in false > # positive results. Ah, thank you. Still, I couldn't reproduce with www-client/chromium-26.0.1403.0. # emerge --info | grep record-gcc-switches CFLAGS="-O2 -march=native -g -pipe -frecord-gcc-switches" CXXFLAGS="-O2 -march=native -g -pipe -frecord-gcc-switches" FCFLAGS="-O2 -pipe -frecord-gcc-switches" FFLAGS="-O2 -pipe -frecord-gcc-switches" (In reply to comment #5) Nor can I. Maybe it has something to do with his more obscure CFLAGS and/or the fact that we call strip-flags in the ebuild. (In reply to comment #6) > (In reply to comment #5) > > Nor can I. Maybe it has something to do with his more obscure CFLAGS and/or > the fact that we call strip-flags in the ebuild. It was strip-flags, thanks! After building with USE=custom-flags I was able to reproduce the message (I think -frecord-gcc-switches can be added to the whitelist btw). QA_FLAGS_IGNORED=".*\.nexe" is sufficient to suppress it, I'm going to commit the change soon. (In reply to comment #7) > (In reply to comment #6) > > (In reply to comment #5) > > > > Nor can I. Maybe it has something to do with his more obscure CFLAGS and/or > > the fact that we call strip-flags in the ebuild. > > It was strip-flags, thanks! After building with USE=custom-flags I was able > to reproduce the message (I think -frecord-gcc-switches can be added to the > whitelist btw). Building sys-libs/glibc with -frecord-gcc-switches may break system. > > QA_FLAGS_IGNORED=".*\.nexe" is sufficient to suppress it, I'm going to > commit the change soon. (In reply to comment #8) > Building sys-libs/glibc with -frecord-gcc-switches may break system. Citation? I'm curious. (In reply to comment #7) > QA_FLAGS_IGNORED=".*\.nexe" is sufficient to suppress it, I'm going to > commit the change soon. Committed for chromium-26+ Thank you for reporting! |