From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Kilian Zinnecker via buildroot <buildroot@buildroot.org>
Cc: Kilian Zinnecker <kilian.zinnecker@mail.de>
Subject: Re: [Buildroot] [PATCH 0/2] Fix Rock 5B build, broken by gcc 12 warnings
Date: Tue, 8 Aug 2023 09:43:48 +0200 [thread overview]
Message-ID: <20230808094348.1c7a8650@windsurf> (raw)
In-Reply-To: <20230808050122.6788-1-kilian.zinnecker@mail.de>
Hello Kilian,
Thanks for your work. See below some comments/questions.
On Tue, 8 Aug 2023 07:01:20 +0200
Kilian Zinnecker via buildroot <buildroot@buildroot.org> wrote:
> Building the image for the Radxa Rock 5B currently breaks: The gcc
> version was recently changed to version 12 and gcc 12 seems to stop
> compiling, if certain warnings occur. See the broken build here:
>
> https://gitlab.com/buildroot.org/buildroot/-/jobs/4795673759
>
> This patch series adds two patches from the mainline Linux kernel,
> which fix two of the warnings. However, also custom code parts of the
> used custom kernel break due to warnings from gcc 12. The best
> solution would be to fix those issues as well. However, until they are
> fixed, the version of gcc used for the Rock 5B is set to the previous
> version, gcc 11.
>
> Kilian Zinnecker (2):
> configs/rock5b: Freeze gcc to version 11
> board/radxa/rock5b: Add patches for gcc12 warnings
I'm not sure to understand the reasoning for the second patch. Does it
fix all gcc 12.x issues or not? If not, what is the motivation for this
second patch?
Also: gcc 11.x is currently the oldest version supported by Buildroot,
it means that as soon as gcc 14.x is released, we will drop support for
gcc 11.x. So clearly, the solution of sticking to gcc 11.x is not going
to work for a very long time.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-08-08 7:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 5:01 [Buildroot] [PATCH 0/2] Fix Rock 5B build, broken by gcc 12 warnings Kilian Zinnecker via buildroot
2023-08-08 5:01 ` [Buildroot] [PATCH 1/2] configs/rock5b: Freeze gcc to version 11 Kilian Zinnecker via buildroot
2023-08-08 5:01 ` [Buildroot] [PATCH 2/2] board/radxa/rock5b: Add patches for gcc12 warnings Kilian Zinnecker via buildroot
2023-08-08 7:43 ` Thomas Petazzoni via buildroot [this message]
2023-08-08 20:44 ` [Buildroot] [PATCH 0/2] Fix Rock 5B build, broken by gcc 12 warnings Kilian Zinnecker via buildroot
2023-08-08 21:19 ` Thomas Petazzoni via buildroot
2023-08-09 5:31 ` Kilian Zinnecker via buildroot
2023-08-12 9:36 ` Kilian Zinnecker via buildroot
2023-08-20 15:29 ` Kilian Zinnecker via buildroot
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=20230808094348.1c7a8650@windsurf \
--to=buildroot@buildroot.org \
--cc=kilian.zinnecker@mail.de \
--cc=thomas.petazzoni@bootlin.com \
/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