Summary: | dev-libs/nss-3.100 doesn't respect CFLAGS | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Arniii <lg3dx6fd> |
Component: | Current packages | Assignee: | Mozilla Gentoo Team <mozilla> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | ionen, lg3dx6fd |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
nss_build.log.lz // to read : ` lzip -dc ./build.log.lz | less `
environment // profile default/linux/amd64/17.1/desktop/plasma gcc-13 O3 pipe march=native(verbose) lto graphite ggdb3 /etc/portage/make.conf |
Description
Arniii
2024-06-02 14:37:42 UTC
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. |