From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-lisp/gcl/
Date: Sat, 29 Jun 2024 10:55:14 +0000 (UTC) [thread overview]
Message-ID: <1719658343.438bbadd0f8ab32907dfd3a3f650f91c35196c76.sam@gentoo> (raw)
commit: 438bbadd0f8ab32907dfd3a3f650f91c35196c76
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Jun 29 10:51:56 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Jun 29 10:52:23 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=438bbadd
dev-lisp/gcl: filter LTO for GCC bug
The code is pretty brittle anyway and we already do strip-flags.
Bug: https://gcc.gnu.org/PR114918
Bug: https://bugs.gentoo.org/931082
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-lisp/gcl/gcl-2.6.13_pre99.ebuild | 1 +
dev-lisp/gcl/gcl-2.6.14.ebuild | 1 +
dev-lisp/gcl/gcl-2.6.15_pre3.ebuild | 1 +
3 files changed, 3 insertions(+)
diff --git a/dev-lisp/gcl/gcl-2.6.13_pre99.ebuild b/dev-lisp/gcl/gcl-2.6.13_pre99.ebuild
index 1673ab7aa83c..d85492310118 100644
--- a/dev-lisp/gcl/gcl-2.6.13_pre99.ebuild
+++ b/dev-lisp/gcl/gcl-2.6.13_pre99.ebuild
@@ -32,6 +32,7 @@ PATCHES=(
)
src_configure() {
+ filter-lto # bug #931082
strip-flags
filter-flags -fstack-protector -fstack-protector-all
# breaks linking on multiple defined syms
diff --git a/dev-lisp/gcl/gcl-2.6.14.ebuild b/dev-lisp/gcl/gcl-2.6.14.ebuild
index fe5638ac7f2c..441d6dcb3be8 100644
--- a/dev-lisp/gcl/gcl-2.6.14.ebuild
+++ b/dev-lisp/gcl/gcl-2.6.14.ebuild
@@ -27,6 +27,7 @@ DEPEND="${RDEPEND}
>=dev-build/autoconf-2.52"
src_configure() {
+ filter-lto # bug #931082
strip-flags
filter-flags -fstack-protector -fstack-protector-all
# breaks linking on multiple defined syms
diff --git a/dev-lisp/gcl/gcl-2.6.15_pre3.ebuild b/dev-lisp/gcl/gcl-2.6.15_pre3.ebuild
index 6473aba4cc59..9d2222ae4c4e 100644
--- a/dev-lisp/gcl/gcl-2.6.15_pre3.ebuild
+++ b/dev-lisp/gcl/gcl-2.6.15_pre3.ebuild
@@ -35,6 +35,7 @@ PATCHES=(
S="${WORKDIR}"/${PN}-Version_2_6_15pre3/${PN}
src_configure() {
+ filter-lto # bug #931082
strip-flags
filter-flags -fstack-protector -fstack-protector-all
next reply other threads:[~2024-06-29 10:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-29 10:55 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-25 16:42 [gentoo-commits] repo/gentoo:master commit in: dev-lisp/gcl/ Jakov Smolić
2023-01-22 6:31 Andrey Grozin
2022-04-17 19:53 Jakov Smolić
2022-04-01 6:26 Ulrich Müller
2022-03-31 20:35 Arthur Zamarin
2022-03-28 9:13 Jakov Smolić
2022-02-17 11:00 Jakov Smolić
2022-02-13 21:08 Conrad Kostecki
2021-03-28 10:44 Andrey Grozin
2021-03-28 9:44 Andrey Grozin
2019-06-03 21:20 Sergei Trofimovich
2018-04-08 7:21 José María Alonso
2018-04-07 21:12 José María Alonso
2017-02-24 7:46 Michael Weber
2015-09-28 5:27 Jeroen Roovers
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=1719658343.438bbadd0f8ab32907dfd3a3f650f91c35196c76.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