From: Kilian Zinnecker via buildroot <buildroot@buildroot.org>
To: Kilian Zinnecker via buildroot <buildroot@buildroot.org>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH 0/2] Fix Rock 5B build, broken by gcc 12 warnings
Date: Sun, 20 Aug 2023 17:29:51 +0200 [thread overview]
Message-ID: <1864236.tdWV9SEqCh@kilian-aisec> (raw)
In-Reply-To: <20230808094348.1c7a8650@windsurf>
Hello Thomas,
[--SNIP--]
> 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.
I was thinking about this again, and I personally think the most cleanest
solution would be to simply disable the custom code parts, which throw
warnings not accepted by gcc 12. In this particular case this basically means
disabling WiFi support for the Rock5b. This is not nice, but I think it is the
cleanest way untill the issues are fixed. I did send a v2 of the patches.
Best regards,
Kilian
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-08-20 15:29 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 ` [Buildroot] [PATCH 0/2] Fix Rock 5B build, broken by gcc 12 warnings Thomas Petazzoni via buildroot
2023-08-08 20:44 ` 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 [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=1864236.tdWV9SEqCh@kilian-aisec \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.