From: Jean Delvare <jdelvare@suse.de>
To: Peter Zijlstra <peterz@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Build breakage caused by the use of UDB
Date: Wed, 17 Dec 2025 23:07:32 +0100 [thread overview]
Message-ID: <20251217230732.1e822263@endymion> (raw)
In-Reply-To: <20251217124713.GD3708021@noisy.programming.kicks-ass.net>
On Wed, 17 Dec 2025 13:47:13 +0100, Peter Zijlstra wrote:
> On Wed, Dec 17, 2025 at 01:35:36PM +0100, Peter Zijlstra wrote:
> > On Wed, Dec 17, 2025 at 12:44:23PM +0100, Jean Delvare wrote:
> > > I must confess this is all way beyond me and I have no idea how this
> > > change can cause such a build failure, but it does. If it matters, my
> > > compiler is gcc 8.2.1.
> >
> > Well, that is somewhat unexpected. None of the build robots fingered
> > this. Is there a particular .config I should try?
> >
> > I don't seem to have 8.2.1 at hand, but I'll try with 8.3.0.
>
> I had to (obviously) enable the RTL8192 bits, but then, yes. gcc-8 fails
> to build this while gcc-10 doesn't seem to have any problems (for some
> reason my random dev machine of the day doesn't seem to have gcc-9).
For the record, gcc 9.3.1 also fails to build kernel v6.18.1, for the
same reason.
--
Jean Delvare
SUSE L3 Support
prev parent reply other threads:[~2025-12-17 22:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 11:44 Build breakage caused by the use of UDB Jean Delvare
2025-12-17 12:35 ` Peter Zijlstra
2025-12-17 12:47 ` Peter Zijlstra
2025-12-17 13:02 ` Peter Zijlstra
2025-12-17 13:34 ` Peter Zijlstra
2025-12-17 14:39 ` Uros Bizjak
2025-12-18 8:54 ` Peter Zijlstra
2025-12-18 10:26 ` Uros Bizjak
2025-12-18 10:38 ` Peter Zijlstra
2025-12-18 10:46 ` Peter Zijlstra
2025-12-18 11:03 ` [tip: x86/urgent] x86/bug: Fix old GCC compile fails tip-bot2 for Peter Zijlstra
2025-12-18 12:38 ` Build breakage caused by the use of UDB Brian Gerst
2025-12-17 13:10 ` Jean Delvare
2025-12-17 13:22 ` Peter Zijlstra
2025-12-17 22:07 ` Jean Delvare [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251217230732.1e822263@endymion \
--to=jdelvare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox