From: Jason Montleon <jmontleo@redhat.com>
To: ojeda@kernel.org, alex.gaynor@gmail.com, boqun.feng@gmail.com,
gary@garyguo.net, bjorn3_gh@protonmail.com,
benno.lossin@proton.me, a.hindborg@kernel.org,
aliceryhl@google.com, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, nathan@kernel.org,
ndesaulniers@google.com, morbo@google.com,
justinstitt@google.com
Cc: rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, llvm@lists.linux.dev,
Jason Montleon <jmontleo@redhat.com>
Subject: [PATCH 0/1] RISC-V: Fix building rust when using GCC toolchain
Date: Mon, 16 Sep 2024 20:08:47 -0400 [thread overview]
Message-ID: <20240917000848.720765-1-jmontleo@redhat.com> (raw)
The following patch resolves errors encountered while building on RISC-V
using the gcc toolchain with RUST_CONFIG=y
Jason Montleon (1):
RISC-V: Fix building rust when using GCC toolchain
rust/Makefile | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
base-commit: ad060dbbcfcfcba624ef1a75e1d71365a98b86d8
--
2.46.0
next reply other threads:[~2024-09-17 0:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 0:08 Jason Montleon [this message]
2024-09-17 0:08 ` [PATCH] RISC-V: Fix building rust when using GCC toolchain Jason Montleon
2024-09-17 9:35 ` Conor Dooley
2024-09-17 13:29 ` Gary Guo
2024-09-17 15:26 ` Conor Dooley
2024-09-26 15:40 ` Miguel Ojeda
2024-09-26 15:56 ` Conor Dooley
2024-09-26 16:11 ` Miguel Ojeda
2024-09-26 16:21 ` Conor Dooley
2024-09-26 16:29 ` Miguel Ojeda
2024-09-17 13:32 ` Gary Guo
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=20240917000848.720765-1-jmontleo@redhat.com \
--to=jmontleo@redhat.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=aou@eecs.berkeley.edu \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ojeda@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rust-for-linux@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).