From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: x11-libs/fox/
Date: Sat, 27 Jul 2024 22:47:43 +0000 (UTC) [thread overview]
Message-ID: <1722118773.fe5777553eb7e9cf64c0526ba194b831cb455f38.sam@gentoo> (raw)
commit: fe5777553eb7e9cf64c0526ba194b831cb455f38
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Jul 27 22:19:33 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Jul 27 22:19:33 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fe577755
x11-libs/fox: filter LTO
Has strict aliasing issues. The website has:
> Tentative alias_cast() template may be used for shutting up GCC alias warnings. This means type-punning related warnings are now properly suppressed.
which isn't promising.
Signed-off-by: Sam James <sam <AT> gentoo.org>
x11-libs/fox/fox-1.7.84.ebuild | 2 ++
1 file changed, 2 insertions(+)
diff --git a/x11-libs/fox/fox-1.7.84.ebuild b/x11-libs/fox/fox-1.7.84.ebuild
index 33e6f56e8667..baab848c2236 100644
--- a/x11-libs/fox/fox-1.7.84.ebuild
+++ b/x11-libs/fox/fox-1.7.84.ebuild
@@ -65,6 +65,8 @@ src_prepare() {
}
src_configure() {
+ filter-lto
+
use debug || append-cppflags -DNDEBUG
# Not using --enable-release because of the options it sets like no SSP
next reply other threads:[~2024-07-27 22:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-27 22:47 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-09 10:48 [gentoo-commits] repo/gentoo:master commit in: x11-libs/fox/ Sam James
2024-10-09 10:48 Sam James
2024-10-09 10:48 Sam James
2024-10-09 10:48 Sam James
2024-10-09 10:48 Sam James
2024-04-05 1:21 Sam James
2024-03-08 11:09 Sam James
2024-03-08 11:09 Sam James
2022-12-18 8:20 Sam James
2022-12-18 8:06 Sam James
2022-12-16 1:40 Sam James
2021-12-08 3:33 Sam James
2021-12-08 3:33 Sam James
2021-07-04 22:17 Sam James
2021-07-04 22:17 Sam James
2019-12-30 14:11 Jason A. Donenfeld
2019-12-30 14:00 David Seifert
2019-12-30 12:18 Jason A. Donenfeld
2019-12-28 8:23 Jason A. Donenfeld
2019-02-26 20:54 Andreas Sturmlechner
2018-03-23 23:11 Sergei Trofimovich
2017-06-15 14:23 Anthony G. Basile
2017-06-13 12:31 Agostino Sarubbo
2016-12-25 10:23 Agostino Sarubbo
2016-12-22 8:57 Agostino Sarubbo
2016-12-20 16:52 Tobias Klausmann
2016-08-06 10:51 Pacho Ramos
2016-01-07 10:55 Lars Wendler
2015-11-25 12:03 Lars Wendler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1722118773.fe5777553eb7e9cf64c0526ba194b831cb455f38.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox