From: Igor Korotin <igor.korotin@yahoo.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
rust-for-linux@vger.kernel.org
Subject: Re: [PATCH v2] docs: rust: quick-start: update Ubuntu instructions
Date: Wed, 2 Apr 2025 14:52:40 +0100 [thread overview]
Message-ID: <29f73af3-e097-4c7d-889c-394ae1d2d961@yahoo.com> (raw)
In-Reply-To: <CANiq72mysmMph1zGAxPKDY_FixbRRa0kS3pSqj4Qhq6Yjqq2AA@mail.gmail.com>
On 4/2/25 12:26, Miguel Ojeda wrote:
> Also, weren't we going to mention `RUSTDOC`, `RUSTFMT` and `CLIPPY_DRIVER`?
While re-writing my changes I found out that while packages rustc,
rustdoc and
rustfmt of version 1.80 in 22.04 and 24.04 at least create symbolic
links to
their tools in /usr/bin/, rust-1.80-clippy does not do it. So the
clippy-driver
is only accessible by its full path /usr/lib/rust-1.80/bin/clippy-driver.
I'm sure this quick-start.rst should be updated, because from my
experience I know that it is painful for newcomer to configure Rust for
kernel properly in Ubuntu 22.04/24.04. And to be honest, I see
`PATH=/usr/lib/rust-1.80/bin:$PATH` the easiest solution. Rust packages
in 22.04/24.04 are screwed. I checked 24.10/25.04 and these versions do
not have such problems at all, it's just enough to use `apt rustc
rustdoc rustfmt bindgen rust-clippy` to install rust 1.84 and bindgen
0.71 and set `RUST_LIB_SRC` variable.
Best Regards
Igor
next prev parent reply other threads:[~2025-04-02 13:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250402104759.1764282-1-igor.korotin.ref@yahoo.com>
2025-04-02 10:47 ` [PATCH v2] docs: rust: quick-start: update Ubuntu instructions Igor Korotin
2025-04-02 11:26 ` Miguel Ojeda
2025-04-02 11:49 ` Igor Korotin
2025-04-02 16:06 ` Miguel Ojeda
2025-04-02 13:52 ` Igor Korotin [this message]
2025-04-02 16:06 ` Miguel Ojeda
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=29f73af3-e097-4c7d-889c-394ae1d2d961@yahoo.com \
--to=igor.korotin@yahoo.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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