flag-o-matic.eclass: allow -ffat-lto-objects in strip-flags

This flag is "safe" for the same reason `-flto` is "safe". Furthermore,
the new dot-a.eclass relies on setting this flag, which `strip-flags` then
deletes again in the event that a package uses both `lto-guarantee-fat` and
`strip-flags`.

End result: static libraries that contain neither LTO nor regular object
code.

Example package that does this: dev-libs/nss

Acked-by: Sam James <sam@gentoo.org>
Signed-off-by: Eli Schwartz <eschwartz@gentoo.org>
This commit is contained in:
Eli Schwartz 2025-05-06 11:53:40 -04:00
parent a07f997c52
commit a13d692939
No known key found for this signature in database
GPG Key ID: 84A7D12B700D2F57

View File

@ -46,7 +46,7 @@ setup-allowed-flags() {
_setup-allowed-flags() {
ALLOWED_FLAGS=(
-pipe -O '-O[123szg]' '-mcpu=*' '-march=*' '-mtune=*' '-mfpmath=*'
-flto '-flto=*' -fno-lto
-flto '-flto=*' -fno-lto -ffat-lto-objects
# Hardening flags
'-fstack-protector*'