public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Miguel Ojeda <ojeda@kernel.org>
To: "Christian Schrrefl" <chrisi.schrefl@gmail.com>,
	"Russell King" <rmk+kernel@armlinux.org.uk>,
	"Fabian Grünbichler" <debian@fabian.gruenbichler.email>
Cc: Rudraksha Gupta <guptarud@gmail.com>,
	Ard Biesheuvel <ardb@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	Miguel Ojeda <ojeda@kernel.org>,
	rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: arm `rustdoc` Rust 1.85.0-only build error
Date: Tue, 31 Mar 2026 21:00:53 +0200	[thread overview]
Message-ID: <20260331190053.482607-1-ojeda@kernel.org> (raw)

Hi Christian, Russell, arm, Fabian,

For Rust 1.85.0, for arm32, for the `rustdoc` target (i.e. all those
combined), I am seeing:

      RUSTDOC   .../1.85.0-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/lib.rs
    error: target feature `fp-armv8` cannot be toggled with `#[target_feature]`: Rust ties `fp-armv8` to `neon`
        --> .../1.85.0-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/../../stdarch/crates/core_arch/src/arm_shared/neon/generated.rs:7538:48
         |
    7538 | #[cfg_attr(target_arch = "arm", target_feature(enable = "fp-armv8,v8"))]
         |                                                ^^^^^^^^^^^^^^^^^^^^^

The issue is [1], was introduced in Rust 1.85.0 and was fixed already in
Rust 1.85.1 [2]:

  Link: https://github.com/rust-lang/rust/issues/137366 [1]
  Link: https://github.com/rust-lang/rust/pull/137632 [2]

It is unfortunate since our minimum is going to be 1.85.0 since that is
what Debian Stable has (even if patches may be on top) -- I generally
test the latest patch versions for each minor, but I noticed this since
I also test the actual minimum, and I am bumping it to 1.85.0.

To be clear, it is likely almost no one actually cares about this, since
nobody complained yet, and this can easily be fixed using the already
released Rust 1.85.1.

By the way, what is Debian's policy on upstream Rust patch versions?

Thanks!

Cheers,
Miguel


             reply	other threads:[~2026-03-31 19:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-31 19:00 Miguel Ojeda [this message]
2026-04-03  8:12 ` arm `rustdoc` Rust 1.85.0-only build error Fabian Grünbichler
2026-04-03 10:19   ` Miguel Ojeda
2026-04-03 12:48   ` Gary Guo

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=20260331190053.482607-1-ojeda@kernel.org \
    --to=ojeda@kernel.org \
    --cc=ardb@kernel.org \
    --cc=chrisi.schrefl@gmail.com \
    --cc=debian@fabian.gruenbichler.email \
    --cc=guptarud@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=rust-for-linux@vger.kernel.org \
    /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