[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72mXCS=OnrPd9p5RpkMVRZFjf+JBEyg3MdZLqkbMEZs6dQ@mail.gmail.com>
Date: Thu, 7 Nov 2024 16:05:30 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Eder Zulian <ezulian@...hat.com>
Cc: Boqun Feng <boqun.feng@...il.com>, Peter Zijlstra <peterz@...radead.org>,
Stephen Rothwell <sfr@...b.auug.org.au>, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, "H. Peter Anvin" <hpa@...or.com>, Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Subject: Re: linux-next: build failure after merge of the tip tree
On Thu, Nov 7, 2024 at 4:01 PM Eder Zulian <ezulian@...hat.com> wrote:
>
> By the way, I'm using linux-next/master here and I think I had to make
> (MITIGATION_RETHUNK && KASAN) false at some point for x86_64 to get RUST=y.
Yeah, that would be this one:
depends on !(MITIGATION_RETHUNK && KASAN) || RUSTC_VERSION >= 108300
i.e. it can be avoided with Rust 1.83, to be released in 3 weeks (2024-11-28).
Cheers,
Miguel
Powered by blists - more mailing lists