[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231215112418.usky65sibhbiubyx@vireshk-i7>
Date: Fri, 15 Dec 2023 16:54:18 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Tiago Lam <tiagolam@...il.com>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>,
Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>,
Wedson Almeida Filho <wedsonaf@...il.com>,
Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <benno.lossin@...ton.me>,
Andreas Hindborg <a.hindborg@...sung.com>,
Alice Ryhl <aliceryhl@...gle.com>, Jonathan Corbet <corbet@....net>,
Vincent Guittot <vincent.guittot@...aro.org>,
rust-for-linux@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH V2] docs: rust: Clarify that 'rustup override' applies to
build directory
On 15-12-23, 11:14, Tiago Lam wrote:
> If ``rustup`` is being used, enter the checked out source code directory,
> or your build directory (if you're using the `O=` option to build the
> kernel), and run::
I thought people aren't required to enter the build directory now (but
just source code directory) and simply do:
make LLVM=1 O=<builddir> rustupoverride
>
> make LLVM=1 rustupoverride
Will this still work if we are in the build directory ?
> This will configure your current directory to use the correct version of
> ``rustc`` without affecting your default toolchain.
>
> If you are not using ``rustup``, fetch a standalone installer from:
>
> https://forge.rust-lang.org/infra/other-installation-methods.html#standalone
--
viresh
Powered by blists - more mailing lists