From: Arthur Cohen <arthur.cohen@embecosm.com>
To: gcc-patches@gcc.gnu.org, rguenther@suse.de
Cc: gcc-rust@gcc.gnu.org
Subject: [PATCHSET] Fix Rust bootstrap for future libgrust changes
Date: Thu, 11 Jan 2024 15:22:07 +0100 [thread overview]
Message-ID: <20240111142355.1110429-2-arthur.cohen@embecosm.com> (raw)
Hi everyone,
Sorry about this - two simple changes to Makefile.def we had missed
during our first libgrust/ patchset, plus the associated regen of
Makefile.in in each commit.
Let me know if I should squash them together. I'll follow them up
with our entire patchset.
Best,
Arthur
next reply other threads:[~2024-01-11 14:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 14:22 Arthur Cohen [this message]
2024-01-11 14:22 ` [PATCH 1/2] gccrs: fixup: Fix bootstrap build Arthur Cohen
2024-01-11 14:22 ` [PATCH 2/2] gccrs: fixup: Fix missing build dependency Arthur Cohen
2024-01-11 14:23 ` Richard Biener
2024-01-11 14:32 ` Arthur Cohen
2024-01-11 14:30 ` Richard Biener
2024-01-12 0:02 ` [PATCHSET] Fix Rust bootstrap for future libgrust changes Thomas Schwinge
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=20240111142355.1110429-2-arthur.cohen@embecosm.com \
--to=arthur.cohen@embecosm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc-rust@gcc.gnu.org \
--cc=rguenther@suse.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).