[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241107143930.GC38786@noisy.programming.kicks-ass.net>
Date: Thu, 7 Nov 2024 15:39:30 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: 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>,
bigeasy@...utronix.de, boqun.feng@...il.com
Subject: Re: linux-next: build failure after merge of the tip tree
On Thu, Nov 07, 2024 at 03:31:27PM +0100, Miguel Ojeda wrote:
> On Thu, Nov 7, 2024 at 11:34 AM Peter Zijlstra <peterz@...radead.org> wrote:
> >
> > So I can't get RUST=y, even though make rustavailable is happy.
>
> If you get the chance, please check in e.g. `menuconfig` the unmet `depends on`.
>
> It could be e.g. the `!CALL_PADDING` one if you have an older `rustc`
> than Stephen.
So menuconfig prints that as a giant line without wrapping, but instead
forces me to press 'right-arrow' to scrol that.
So I can't readily read or even copy/paste it :-(
http://peterz.broke-it.net/sekrit/allmodconfig
Is what I get from: make LLVM=-19 allmodconfig
It has:
CONFIG_RUSTC_VERSION=108200
Which is what I installed today from debian/unstable, because the
version from debian/testing was too old to satisfy make rustavailable.
Powered by blists - more mailing lists