IDK if such stuff should be reported here, but on IRC nobody answered that. * Messages for package dev-libs/nss-3.100: * QA Notice: Files built without respecting CFLAGS have been detected * Please include the following list of files in your report: * /usr/lib64/libfreebl3.so * /usr/lib64/libfreeblpriv3.so * /usr/lib64/libnss3.so * /usr/lib64/libnssckbi-testlib.so * /usr/lib64/libnssckbi.so * /usr/lib64/libnssdbm3.so * /usr/lib64/libnsssysinit.so * /usr/lib64/libnssutil3.so * /usr/lib64/libsmime3.so * /usr/lib64/libsoftokn3.so * /usr/lib64/libssl3.so
Please attach the build log and provide emerge --info. Then change the status to UNCONFIRMED.
Haven't tried, but note that using lto often trips up the cflags check, not that can tell if it's used without emerge --info and build.log. *FLAGS checks are normally automatically reported by tinderboxes, which is why I assume there's something else going on.
Created attachment 894990 [details] nss_build.log.lz // to read : ` lzip -dc ./build.log.lz | less `
Created attachment 894991 [details] environment // profile default/linux/amd64/17.1/desktop/plasma gcc-13 O3 pipe march=native(verbose) lto graphite ggdb3
Created attachment 894992 [details] /etc/portage/make.conf
Also I thought that emerge --info is bad because it doesn't show changes if a package is using a /etc/portage/env/* on top of /etc/portage/make.conf . That's why I think `environment` file is the truth.
