From: "Eli Schwartz" <eschwartz@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-lang/qu-prolog/
Date: Wed, 7 Aug 2024 02:17:31 +0000 (UTC) [thread overview]
Message-ID: <1722997037.6194f5483abd98ed4bccbda0d3accfbacfe8b0dd.eschwartz@gentoo> (raw)
commit: 6194f5483abd98ed4bccbda0d3accfbacfe8b0dd
Author: Eli Schwartz <eschwartz <AT> gentoo <DOT> org>
AuthorDate: Wed Aug 7 02:06:26 2024 +0000
Commit: Eli Schwartz <eschwartz <AT> gentoo <DOT> org>
CommitDate: Wed Aug 7 02:17:17 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6194f548
dev-lang/qu-prolog: mark as LTO-unsafe, strict-aliasing unsafe
Closes: https://bugs.gentoo.org/924768
Signed-off-by: Eli Schwartz <eschwartz <AT> gentoo.org>
dev-lang/qu-prolog/qu-prolog-10.7.ebuild | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/dev-lang/qu-prolog/qu-prolog-10.7.ebuild b/dev-lang/qu-prolog/qu-prolog-10.7.ebuild
index bc555920919e..c95725083732 100644
--- a/dev-lang/qu-prolog/qu-prolog-10.7.ebuild
+++ b/dev-lang/qu-prolog/qu-prolog-10.7.ebuild
@@ -5,7 +5,7 @@ EAPI=8
PYTHON_COMPAT=( python3_{10..12} )
-inherit autotools python-any-r1 qmake-utils
+inherit autotools flag-o-matic python-any-r1 qmake-utils
MY_P=qp${PV}
@@ -46,6 +46,13 @@ src_prepare() {
}
src_configure() {
+ # -Werror=strict-aliasing
+ # https://bugs.gentoo.org/924768
+ # Upstream's sole provided contact method is email. I have sent an email
+ # describing the issue. -- Eli
+ append-flags -fno-strict-aliasing
+ filter-lto
+
econf \
--libdir=/usr/$(get_libdir) \
$(use_enable debug) \
next reply other threads:[~2024-08-07 2:17 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 2:17 Eli Schwartz [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-06 20:19 [gentoo-commits] repo/gentoo:master commit in: dev-lang/qu-prolog/ Sam James
2025-01-06 20:19 Sam James
2025-01-06 20:19 Sam James
2024-08-07 2:21 Eli Schwartz
2024-08-07 2:21 Eli Schwartz
2024-07-29 10:51 Pacho Ramos
2022-05-21 6:03 Keri Harris
2021-05-14 0:22 Sam James
2021-05-08 15:21 Keri Harris
2021-01-18 16:00 Keri Harris
2021-01-07 12:30 Sam James
2021-01-07 1:08 Sam James
2021-01-07 0:58 Sam James
2020-09-11 14:59 Keri Harris
2020-07-20 19:37 Keri Harris
2020-07-19 7:43 Agostino Sarubbo
2020-07-17 15:09 Agostino Sarubbo
2020-07-17 7:03 Keri Harris
2020-06-13 10:25 Keri Harris
2020-05-27 16:12 Keri Harris
2020-05-27 16:03 Keri Harris
2018-09-09 1:12 Thomas Deutschmann
2018-09-07 22:54 Sergei Trofimovich
2018-09-03 7:09 Keri Harris
2018-04-01 17:34 Andreas Sturmlechner
2018-04-01 13:47 Sergei Trofimovich
2018-02-21 3:01 Thomas Deutschmann
2018-02-20 14:09 Keri Harris
2017-09-23 14:32 Thomas Deutschmann
2017-09-23 12:35 Sergei Trofimovich
2017-09-22 14:32 Keri Harris
2017-08-01 16:39 Keri Harris
2016-10-03 11:50 Keri Harris
2016-02-15 18:05 Keri Harris
2016-02-14 11:04 Keri Harris
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=1722997037.6194f5483abd98ed4bccbda0d3accfbacfe8b0dd.eschwartz@gentoo \
--to=eschwartz@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