[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72ntZj10H1DBqRyX=uLertMw59e=PM7ESVJ0zWfu_ECnnA@mail.gmail.com>
Date: Fri, 14 Mar 2025 22:36:29 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Masahiro Yamada <masahiroy@...nel.org>
Cc: Thomas Weißschuh <linux@...ssschuh.net>,
Ben Hutchings <ben@...adent.org.uk>, Nathan Chancellor <nathan@...nel.org>,
Nicolas Schier <nicolas@...sle.eu>, Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...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@...nel.org>,
Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>,
Danilo Krummrich <dakr@...nel.org>, linux-kbuild@...r.kernel.org,
linux-kernel@...r.kernel.org, rust-for-linux@...r.kernel.org,
Urgau <urgau@...ericable.fr>
Subject: Re: [PATCH] kbuild, rust: use -fremap-path-prefix to make paths relative
On Thu, Mar 13, 2025 at 1:35 AM Masahiro Yamada <masahiroy@...nel.org> wrote:
>
> Yes, I pushed.
I have noticed in linux-next that the flag triggers an ICE when
building the docs with `O=` -- reduced and reported to upstream here:
https://github.com/rust-lang/rust/issues/138520
Moreover, the flag was only added (to `rustdoc`, not `rustc`) starting
with 1.81.0, so we couldn't pass it anyway unconditionally to
`rustdoc` (it is OK for `rustc`).
In the meantime, the easiest to avoid both issues is to avoid passing
the flag when building docs -- I have sent a patch:
https://lore.kernel.org/rust-for-linux/20250314213333.2230670-1-ojeda@kernel.org/
Cheers,
Miguel
Powered by blists - more mailing lists