From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-lang/ada-bootstrap/
Date: Tue, 1 Oct 2024 08:03:48 +0000 (UTC) [thread overview]
Message-ID: <1727769790.2b7de2c956266fd4748ccffff8bcdff4db15da66.sam@gentoo> (raw)
commit: 2b7de2c956266fd4748ccffff8bcdff4db15da66
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Oct 1 08:01:32 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Oct 1 08:03:10 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2b7de2c9
dev-lang/ada-bootstrap: try harder to strip flags
I can't reproduce the failure reported but let's try this.
Closes: https://bugs.gentoo.org/940599
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-lang/ada-bootstrap/ada-bootstrap-0_p2021-r1.ebuild | 2 ++
1 file changed, 2 insertions(+)
diff --git a/dev-lang/ada-bootstrap/ada-bootstrap-0_p2021-r1.ebuild b/dev-lang/ada-bootstrap/ada-bootstrap-0_p2021-r1.ebuild
index 287f987fce2c..df26633eb5b6 100644
--- a/dev-lang/ada-bootstrap/ada-bootstrap-0_p2021-r1.ebuild
+++ b/dev-lang/ada-bootstrap/ada-bootstrap-0_p2021-r1.ebuild
@@ -140,6 +140,8 @@ src_configure() {
# conservative, we just want it to build for bootstrapping proper
# sys-devel/gcc[ada]. We don't need it to be fast.
strip-flags
+ CC="${WORKDIR}"/${BTSTRP}/bin/gcc strip-unsupported-flags
+ CC="${WORKDIR}"/${GNATDIR}/bin/gcc strip-unsupported-flags
strip-unsupported-flags
filter-lto
append-flags -O2
next reply other threads:[~2024-10-01 8:03 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 8:03 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-24 7:35 [gentoo-commits] repo/gentoo:master commit in: dev-lang/ada-bootstrap/ Sam James
2025-01-23 21:16 Sam James
2025-01-23 6:36 Sam James
2025-01-23 3:02 Sam James
2025-01-22 23:44 Sam James
2025-01-22 19:46 Sam James
2025-01-07 20:09 Sam James
2025-01-05 8:42 WANG Xuerui
2025-01-01 20:09 Sam James
2025-01-01 19:33 Sam James
2025-01-01 19:33 Sam James
2025-01-01 19:33 Sam James
2025-01-01 10:25 Sam James
2025-01-01 10:25 Sam James
2025-01-01 5:15 Sam James
2024-12-31 19:34 Sam James
2024-12-31 19:34 Sam James
2024-12-31 8:12 Sam James
2024-12-31 8:12 Sam James
2024-12-31 8:12 Sam James
2024-12-31 3:18 Jakov Smolić
2024-12-18 23:17 Sam James
2024-12-18 3:15 Sam James
2024-12-18 1:49 Sam James
2024-12-17 19:07 Sam James
2024-12-17 19:00 Sam James
2024-12-17 18:08 Sam James
2024-12-17 12:22 Sam James
2024-12-17 10:57 Sam James
2024-12-17 10:53 Sam James
2024-10-02 1:01 Sam James
2024-10-01 8:03 Sam James
2024-10-01 7:44 Sam James
2024-10-01 7:37 Sam James
2024-10-01 7:32 Sam James
2024-10-01 7:10 Sam James
2024-10-01 6:58 Sam James
2024-10-01 2:06 Sam James
2024-10-01 1:46 Sam James
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=1727769790.2b7de2c956266fd4748ccffff8bcdff4db15da66.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