All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Joao Marcos Costa <joaomarcos.costa@bootlin.com>,
	 quentin.schulz@cherry.de,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 2/3] ovmf: drop gcc-12 specific BUILD_CFLAGS setting
Date: Tue, 12 May 2026 10:51:37 +0100	[thread overview]
Message-ID: <1dbb58318bc8b75f49a0eb892d4774bd345f4e50.camel@linuxfoundation.org> (raw)
In-Reply-To: <fc44ecfe-7502-457b-9dcf-1f63ac4e5fc1@bootlin.com>

On Tue, 2026-05-12 at 11:17 +0200, Joao Marcos Costa wrote:
> Hello,
> 
> On 5/12/26 11:06, Richard Purdie wrote:
> > On Tue, 2026-05-12 at 11:02 +0200, Joao Marcos Costa wrote:
> > > Hello,
> > > 
> > > On 5/12/26 10:46, Richard Purdie wrote:
> > > > On Mon, 2026-05-11 at 16:00 +0200, Joao Marcos Costa via
> > > > lists.openembedded.org wrote:
> > > > > Hello,
> > > > > 
> > > > > On 5/11/26 15:52, Quentin Schulz via lists.openembedded.org
> > > > > wrote:
> > > > > (...)
> > > > > > 
> > > > > > Not necessarily true as I don't think we build GCC for
> > > > > > native recipes
> > > > > > (and ovmf has a native variant), so it depends on the GCC
> > > > > > on the host
> > > > > > (unless you have uninative?). I don't know the autobuilder
> > > > > > infrastructure, e.g. whether we build patches on multiple
> > > > > > workers on
> > > > > > different distros to have a big GCC version test matrix.
> > > > > > 
> > > > > > But yes, building with a newer GCC will generally not make
> > > > > > warnings from
> > > > > > previous versions disappear and I'm hoping upstream has had
> > > > > > time to fix
> > > > > > warnings returned by GCC12 in the last 4 years :)
> > > > > > 
> > > > > > Cheers,
> > > > > > Quentin
> > > > > 
> > > > > Yep, my whole point is based on the the distros in
> > > > > SANITY_TESTED_DISTROS
> > > > > being recent enough to ship GCC > 12 :)
> > > > > 
> > > > > I should have made it explicit in my commit message.
> > > > 
> > > > I hate to say this but:
> > > > 
> > > > Alma/Centos/Rocky 8 have gcc 8
> > > > Debian 11 has gcc 10
> > > > 
> > > > and we don't use buildtools on debian 11.
> > > > 
> > > > I'm therefore not sure how you concluded that from
> > > > SANITY_TESTED_DISTROS.
> > > > 
> > > > Cheers,
> > > > 
> > > > Richard
> > > 
> > > Ah, my bad...
> > > 
> > >   From this list here:
> > > https://docs.yoctoproject.org/ref-manual/system-requirements.html#supported-linux-distributions
> > > 
> > > Considering the versions of Fedora and Ubuntu, I presumed the
> > > other
> > > distros were at least as recent (in terms of packages versions)
> > > as
> > > Fedora 39 (which ships GCC 13).
> > > 
> > > I will check the results in SWAT to see if this warnings pops up,
> > > but
> > > the commit message could use a rewording to address this point
> > > and also
> > > some questions raised by Quentin, so a v2 will be sent later in
> > > this week.
> > 
> > We currently support distros with gcc 10, I think that is clear.
> 
> It is clear, yes, but my point here is the -Wno-error=stringop-
> overflow 
> already being available upstream in the version of edk2 we currently 
> use, and - as per what I understood in their git history - the flag
> was 
> added for the very same reason we have it in the recipe.

Ok, that makes sense. 

Cheers,

Richard


  reply	other threads:[~2026-05-12  9:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11  9:29 [PATCH 0/3] ovmf: add some rework to the recipe João Marcos Costa
2026-05-11  9:29 ` [PATCH 1/3] ovmf: simplify PACKAGECONFIG's default value João Marcos Costa
2026-05-11 13:19   ` Quentin Schulz
2026-05-14 10:57     ` [OE-core] " Ross Burton
2026-05-14 12:40       ` Joao Marcos Costa
2026-05-11  9:29 ` [PATCH 2/3] ovmf: drop gcc-12 specific BUILD_CFLAGS setting João Marcos Costa
2026-05-11 13:27   ` Quentin Schulz
2026-05-11 13:40     ` [OE-core] " Joao Marcos Costa
2026-05-11 13:52       ` Quentin Schulz
2026-05-11 14:00         ` Joao Marcos Costa
2026-05-12  8:46           ` Richard Purdie
2026-05-12  9:02             ` Joao Marcos Costa
2026-05-12  9:06               ` Richard Purdie
2026-05-12  9:17                 ` Joao Marcos Costa
2026-05-12  9:51                   ` Richard Purdie [this message]
2026-05-11  9:29 ` [PATCH 3/3] ovmf: add support for Clang toolchain João Marcos Costa

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=1dbb58318bc8b75f49a0eb892d4774bd345f4e50.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=joaomarcos.costa@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=quentin.schulz@cherry.de \
    /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.