[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72kdCJS9ZDX+6B3pecAbfMqpt2XCqOfQfoKWgLaT9DtMpg@mail.gmail.com>
Date: Mon, 24 Nov 2025 15:48:12 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>, 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 Mon, Nov 24, 2025 at 3:35 PM Peter Zijlstra <peterz@...radead.org> wrote:
>
> 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.
There are several `depends on` for `CONFIG_RUST` as Boqun mentions, so
it is likely one of those is blocking you.
The easiest way to know which one it is is to check what `menuconfig`
computes about the requirements (searching with the `/` command).
Happy to help if that doesn't solve it.
Cheers,
Miguel
Powered by blists - more mailing lists