Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 933424 - dev-libs/nss-3.100 doesn't respect CFLAGS
Summary: dev-libs/nss-3.100 doesn't respect CFLAGS
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Mozilla Gentoo Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-02 14:37 UTC by Arniii
Modified: 2024-10-13 10:19 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
nss_build.log.lz // to read : ` lzip -dc ./build.log.lz | less ` (nss_build.log.lz,197.62 KB, application/x-lzip)
2024-06-03 14:06 UTC, Arniii
Details
environment // profile default/linux/amd64/17.1/desktop/plasma gcc-13 O3 pipe march=native(verbose) lto graphite ggdb3 (file_933424.txt,105.85 KB, text/plain)
2024-06-03 14:07 UTC, Arniii
Details
/etc/portage/make.conf (file_933424.txt,4.28 KB, text/plain)
2024-06-03 14:09 UTC, Arniii
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Arniii 2024-06-02 14:37:42 UTC
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
Comment 1 Mike Gilbert gentoo-dev 2024-06-02 19:09:55 UTC
Please attach the build log and provide emerge --info. Then change the status to UNCONFIRMED.
Comment 2 Ionen Wolkens gentoo-dev 2024-06-02 23:41:41 UTC
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.
Comment 3 Arniii 2024-06-03 14:06:33 UTC
Created attachment 894990 [details]
nss_build.log.lz // to read : ` lzip -dc ./build.log.lz | less `
Comment 4 Arniii 2024-06-03 14:07:09 UTC
Created attachment 894991 [details]
environment // profile default/linux/amd64/17.1/desktop/plasma gcc-13 O3 pipe march=native(verbose) lto graphite ggdb3
Comment 5 Arniii 2024-06-03 14:09:44 UTC
Created attachment 894992 [details]
/etc/portage/make.conf
Comment 6 Arniii 2024-06-03 14:12:07 UTC
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.
Comment 7 Arniii 2024-07-10 08:51:36 UTC
reproducible with dev-libs/nss-3.102
Comment 8 Arniii 2024-10-13 10:19:54 UTC
reproducible with dev-libs/nss-3.105