[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72kkiwaMpeKgNLYiCSMX_VK7a+6Xu4iQrDiB_cpnXpokxg@mail.gmail.com>
Date: Thu, 7 Nov 2024 15:31:27 +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@...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 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.
Cheers,
Miguel
Powered by blists - more mailing lists