From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Guillaume Tucker <gtucker@gtucker.io>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
Miguel Ojeda <ojeda@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
llvm@lists.linux.dev, rust-for-linux@vger.kernel.org,
yurinnick@meta.com, bpf@vger.kernel.org,
Sasha Levin <sashal@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
automated-testing@lists.yoctoproject.org
Subject: Re: Plumbers Testing MC potential topic: specialised toolchains
Date: Tue, 9 Jul 2024 01:07:41 +0200 [thread overview]
Message-ID: <CANiq72mgTiOsnnLUP-JewoFsScV668WstP0bP2Lj+LGxd7L3sg@mail.gmail.com> (raw)
In-Reply-To: <f80acb84-1d98-44d3-84b7-d976de77d8ce@gtucker.io>
Hi Guillaume, all,
A couple of comments on the Rust bits for context.
On Tue, Jul 9, 2024 at 12:10 AM Guillaume Tucker <gtucker@gtucker.io> wrote:
>
> Then Rust support in the kernel is still work-in-progress, so the
> rustc compiler version has to closely follow the kernel revision.
I wouldn't say the reason is that the support in the kernel is
work-in-progress, but rather that `rustc` does not have all the
features the kernel needs (and "stable").
In any case, the version pinning will soon be over -- we are likely
going to have a minimum in v6.11:
https://lore.kernel.org/rust-for-linux/20240701183625.665574-1-ojeda@kernel.org/
We are starting small, but it is already enough to cover the major
rolling distributions: Arch, Fedora, Debian Sid (outside the freeze
period) and perhaps Testing too, Gentoo, Nix unstable, openSUSE
Slowroll and Tumbleweed...
So, for some distributions, the Rust toolchain for the kernel can
already be directly from the distribution. So maybe it doesn't count
as "specialised" anymore? (at least for some distributions)
Of course, I know that you include cutting-edge too :)
> The current state of the art are the kernel.org toolchains:
>
> https://mirrors.edge.kernel.org/pub/tools/
>
> These are for LLVM and cross-compilers, and they already solve a
> large part of the issue described above. However, they don't
> include Rust (yet), and all the dependencies need to be installed
> manually which can have a significant impact on the build
Rust is there thanks to Nathan! :) Please see:
https://mirrors.edge.kernel.org/pub/tools/llvm/rust/
Cheers,
Miguel
next prev parent reply other threads:[~2024-07-08 23:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 22:10 Plumbers Testing MC potential topic: specialised toolchains Guillaume Tucker
2024-07-08 22:22 ` [Automated-testing] " Richard Purdie
2024-07-08 23:07 ` Miguel Ojeda [this message]
2024-07-13 21:25 ` Guillaume Tucker
2024-07-09 5:30 ` Nathan Chancellor
2024-07-13 23:03 ` Guillaume Tucker
2024-09-18 7:33 ` Guillaume Tucker
[not found] ` <17F6464FBF21FF99.27464@lists.yoctoproject.org>
2024-09-30 20:07 ` [Automated-testing] " Guillaume Tucker
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=CANiq72mgTiOsnnLUP-JewoFsScV668WstP0bP2Lj+LGxd7L3sg@mail.gmail.com \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=arnd@arndb.de \
--cc=ast@kernel.org \
--cc=automated-testing@lists.yoctoproject.org \
--cc=bpf@vger.kernel.org \
--cc=gtucker@gtucker.io \
--cc=llvm@lists.linux.dev \
--cc=ndesaulniers@google.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=yurinnick@meta.com \
/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).