https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: dev-libs/bitset-2.8.4-r1 does not respect CFLAGS. Discovered on: amd64 (internal ref: tinderbox) NOTE: To reproduce this issue you may want to add "-frecord-gcc-switches" to CFLAGS/CXXFLAGS/FFLAGS/FCFLAGS. If this is not something about c/c++ context see this bug as an hint to hide the QA warning (with QA_FLAGS_IGNORED) where is not possible to respect CFLAGS.
Created attachment 742380 [details] build.log build log and emerge --info
Somehow CFLAGS are not detected by package buildsystem, thus it tries to put 'good' CFLAGS itself. I can not reproduce it on my system, i just do not have strings like: checking whether C compiler accepts -malign-double... yes checking whether C compiler accepts -fstrict-aliasing... yes checking whether C compiler accepts -ffast-math... yes during configure stage, and those options does not added into CFLAGS. But i discovered option --enable-portable-binary, which, based on it's description will reduce 'smartness' of buildsystem in case if it can not detect user requested CFLAGS. Please try dev-libs/bitset-2.8.4-r2, thanks in advance
ci has reproduced this issue with version 2.8.4-r2 - Updating summary.
I have narrowed down problem to sys-devel/autoconf:2.71 -> when it is used, CFLAGS are ignored by package buildsystem
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=13d1897a864185b16ce8bcf8256d689efdf35372 commit 13d1897a864185b16ce8bcf8256d689efdf35372 Author: Sergey Popov <pinkbyte@gentoo.org> AuthorDate: 2021-10-04 10:47:07 +0000 Commit: Sergey Popov <pinkbyte@gentoo.org> CommitDate: 2021-10-04 10:48:04 +0000 dev-libs/bitset: revision bump Yet another attemp to fix CFLAGS handling Bug: https://bugs.gentoo.org/815637 Package-Manager: Portage-3.0.20, Repoman-3.0.3 Signed-off-by: Sergey Popov <pinkbyte@gentoo.org> dev-libs/bitset/{bitset-2.8.4-r2.ebuild => bitset-2.8.4-r3.ebuild} | 5 +++++ 1 file changed, 5 insertions(+)
