Re: linux-next: build failure after merge of the tip tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: linux-next: build failure after merge of the tip tree
From: Miguel Ojeda <miguel.ojeda.sandonis@xxxxxxxxx>
Date: Thu, 7 Nov 2024 15:31:27 +0100
Cc: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxxxxx>, "H. Peter Anvin" <hpa@xxxxxxxxx>, Miguel Ojeda <ojeda@xxxxxxxxxx>, Alex Gaynor <alex.gaynor@xxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Linux Next Mailing List <linux-next@xxxxxxxxxxxxxxx>, bigeasy@xxxxxxxxxxxxx, boqun.feng@xxxxxxxxx
In-reply-to: <20241107103414.GT10375@noisy.programming.kicks-ass.net>
References: <20241107182411.57e2b418@canb.auug.org.au> <20241107103414.GT10375@noisy.programming.kicks-ass.net>

On Thu, Nov 7, 2024 at 11:34 AM Peter Zijlstra <peterz@xxxxxxxxxxxxx> 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

Follow-Ups:
- Re: linux-next: build failure after merge of the tip tree
  - From: Peter Zijlstra

References:
- linux-next: build failure after merge of the tip tree
  - From: Stephen Rothwell
- Re: linux-next: build failure after merge of the tip tree
  - From: Peter Zijlstra

Prev by Date: Re: linux-next: build failure after merge of the tip tree
Next by Date: Re: linux-next: build failure after merge of the tip tree
Previous by thread: Re: linux-next: build failure after merge of the tip tree
Next by thread: Re: linux-next: build failure after merge of the tip tree
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel] [Linux USB Development] [Yosemite News] [Linux SCSI]

Powered by Linux