[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72=JNS8eaQXJYCTNw8vNymD-0A-g4FmagyLkaH7L1DqhwA@mail.gmail.com>
Date: Thu, 26 Sep 2024 18:29:28 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Conor Dooley <conor@...nel.org>
Cc: Gary Guo <gary@...yguo.net>, Jason Montleon <jmontleo@...hat.com>, ojeda@...nel.org,
alex.gaynor@...il.com, boqun.feng@...il.com, bjorn3_gh@...tonmail.com,
benno.lossin@...ton.me, a.hindborg@...nel.org, aliceryhl@...gle.com,
paul.walmsley@...ive.com, palmer@...belt.com, aou@...s.berkeley.edu,
nathan@...nel.org, ndesaulniers@...gle.com, morbo@...gle.com,
justinstitt@...gle.com, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-riscv@...ts.infradead.org,
llvm@...ts.linux.dev, stable@...r.kernel.org
Subject: Re: [PATCH] RISC-V: Fix building rust when using GCC toolchain
On Thu, Sep 26, 2024 at 6:21 PM Conor Dooley <conor@...nel.org> wrote:
>
> No. Things like clang + ld & gas.
> I don't care about out of tree modules ;)
Ah, other tools, not just the C compiler, I see -- that is why I
mentioned out-of-tree modules, because otherwise I was not sure how
you would get mix the C compiler itself, i.e. GCC and Clang.
> Yes, just for riscv. The logic in our Kconfig menu is currently something
> like
> select HAVE_RUST if RUSTC_SUPPORTS_RISCV
> so that would just become
> select HAVE_RUST if RUSTC_SUPPORTS_RISCV && CC_IS_CLANG
If that is what you think it is best for RISC-V, then sure, up to you -- thanks!
Cheers,
Miguel
Powered by blists - more mailing lists