All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kilian Zinnecker via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org, Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH 0/2] Fix Rock 5B build, broken by gcc 12 warnings
Date: Sat, 12 Aug 2023 11:36:09 +0200	[thread overview]
Message-ID: <1859651.tdWV9SEqCh@kilian-aisec> (raw)
In-Reply-To: <20230808231913.1d0a98e1@windsurf>

Hello Thomas,

[--SNIP--]

> > Thanks for the info, I actually would not have known this! I think that
> > the
> > best way is to ask the maintainers of the Radxa custom kernel whether they
> > may fix the remaining issues, so that the custom kernel compiles with gcc
> > 12.x. I intend to do so.
> 
> ACK.

I opened up an issue in their git about this. However, I must admit, I really 
doubt, that the Radxa people fix the warnings in their kernel in time for the 
next buildroot release, or even at all: They seem to have issues, reported 
last december, in their git, which they yet did not reply to. Now, I could 
give it a try and try to fix the warnigs of their custom code, but at the 
moment, I don't have the time, and I would rather like to focus on the 
BeagleV-Ahead board support :)

So I would argue to simply fix the gcc version to 11x for now:

1. I think this is legit in such cases - why else would the option even exist 
in buildroot.

2. Even if version 11 of gcc will be removed in the near future, we would then 
at least have one release version of buildroot, which features the Rock 5B. I 
think that would be a plus for makers, hobbyists and professionals, e.g., who 
use the Rock 5B to evaluate the RK3588 (I actually know one person who used 
the Rock 5B for such purposes). Also, maybe in the future I find time to 
prepare some patches, or maybe the Radxa people also fix it till then.

[--SNIP--]

Best regards,
Kilian




_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2023-08-12  9:36 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 [this message]
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=1859651.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.