commit: 9da7e1e40003ff669572d9dd47f11aedd8852f2e Author: Eli Schwartz <eschwartz93 <AT> gmail <DOT> com> AuthorDate: Wed Mar 13 06:16:54 2024 +0000 Commit: Sam James <sam <AT> gentoo <DOT> org> CommitDate: Wed Mar 13 21:04:05 2024 +0000 URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9da7e1e4
dev-libs/nspr: mark as LTO-unsafe, strict-aliasing unsafe It is a testsuite-only issue. We think, because it prevents, well, testing. Closes: https://bugs.gentoo.org/867634 Signed-off-by: Eli Schwartz <eschwartz93 <AT> gmail.com> Signed-off-by: Sam James <sam <AT> gentoo.org> dev-libs/nspr/nspr-4.35-r2.ebuild | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/dev-libs/nspr/nspr-4.35-r2.ebuild b/dev-libs/nspr/nspr-4.35-r2.ebuild index ec3cb17b0172..01df06b9ec19 100644 --- a/dev-libs/nspr/nspr-4.35-r2.ebuild +++ b/dev-libs/nspr/nspr-4.35-r2.ebuild @@ -62,6 +62,14 @@ src_prepare() { } multilib_src_configure() { + # -Werror=strict-aliasing + # https://bugs.gentoo.org/867634 + # + # Testsuite-only issue. Still, this makes it challenging to test the package with LTO + # enabled... + append-flags -fno-strict-aliasing + filter-lto + # The build system overrides user optimization level based on a configure flag. #886987 local my_optlvl=$(get-flag '-O*')
