From: "Gary Guo" <gary@garyguo.net>
To: "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nicolas Schier" <nicolas@fjasle.eu>
Cc: "Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"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, linux-kbuild@vger.kernel.org,
"David Wood" <david@davidtw.co>,
"Wesley Wiser" <wwiser@gmail.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] rust: kbuild: pass `-Zunstable-options` for Rust 1.95.0
Date: Fri, 06 Feb 2026 21:15:22 +0000 [thread overview]
Message-ID: <DG86V0YSM7W8.2SNKPBF9ZJC7X@garyguo.net> (raw)
In-Reply-To: <20260206204535.39431-1-ojeda@kernel.org>
On Fri Feb 6, 2026 at 8:45 PM GMT, Miguel Ojeda wrote:
> Custom target specifications are unstable, but starting with Rust 1.95.0,
> `rustc` requires to explicitly pass `-Zunstable-options` to use them [1]:
>
> error: error loading target specification: custom targets are unstable and require `-Zunstable-options`
> |
> = help: run `rustc --print target-list` for a list of built-in targets
>
> David (Rust compiler team lead), writes:
>
> "We're destabilising custom targets to allow us to move forward with
> build-std without accidentally exposing functionality that we'd like
> to revisit prior to committing to. I'll start a thread on Zulip to
> discuss with the RfL team how we can come up with an alternative
> for them."
>
> Thus pass it.
>
> Cc: David Wood <david@davidtw.co>
> Cc: Wesley Wiser <wwiser@gmail.com>
> Cc: stable@vger.kernel.org # Needed in 6.12.y and later (Rust is pinned in older LTSs).
> Link: https://github.com/rust-lang/rust/pull/151534 [1]
> Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
I can confirm that build will fail on x64 without this patch in latest nightly
and this fixed it.
Reviewed-by: Gary Guo <gary@garyguo.net>
Tested-by: Gary Guo <gary@garyguo.net>
> ---
> rust/Makefile | 3 +++
> 1 file changed, 3 insertions(+)
next prev parent reply other threads:[~2026-02-06 21:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 20:45 [PATCH] rust: kbuild: pass `-Zunstable-options` for Rust 1.95.0 Miguel Ojeda
2026-02-06 20:58 ` Miguel Ojeda
2026-02-06 21:15 ` Gary Guo [this message]
2026-02-10 8:42 ` 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=DG86V0YSM7W8.2SNKPBF9ZJC7X@garyguo.net \
--to=gary@garyguo.net \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=david@davidtw.co \
--cc=linux-kbuild@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=nathan@kernel.org \
--cc=nicolas@fjasle.eu \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=wwiser@gmail.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