[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251124143537.GS3245006@noisy.programming.kicks-ass.net>
Date: Mon, 24 Nov 2025 15:35:37 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...nel.org>,
"H. Peter Anvin" <hpa@...or.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
ojeda@...nel.org, boqun.feng@...il.com
Subject: Re: linux-next: build failure after merge of the tip tree
On Tue, Nov 25, 2025 at 01:03:51AM +1100, Stephen Rothwell wrote:
> Hi Peter,
>
> On Mon, 24 Nov 2025 13:32:49 +0100 Peter Zijlstra <peterz@...radead.org> wrote:
> >
> > Rust :/
> >
> > So I have:
> >
> > $ make O=tmp-build LLVM=-22 allmodconfig
> > $ make O=tmp-build LLVM=-22 rustavailable
> > Rust is available!
> > $ grep -e CONFIG_RUST= -e CONFIG_NOVA= tmp-build/.config
> > $
> >
> > Help ?!?
>
> Have you read Documentation/rust/quick-start.rst?
At some point in the past... I just did again, and updated the relevant
packages and rustavailable is still green, but allmodconfig is still not
giving me rust.
I'm on Debian Testing.
Powered by blists - more mailing lists