From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] gcc: upgrade 11.3 -> 12.1
Date: Tue, 10 May 2022 12:37:18 +0200 [thread overview]
Message-ID: <20220510123718.451b33ef@melee> (raw)
In-Reply-To: <CAMKF1sofg6oc_gKhWZ_RtVqLiH5ZwwfLvO9Y+2=dAfMRSAonmg@mail.gmail.com>
Hi Khem,
Il giorno Mon, 9 May 2022 16:59:02 -0700
Khem Raj <raj.khem@gmail.com> ha scritto:
> On Mon, May 9, 2022 at 2:39 PM Luca Ceresoli
> <luca.ceresoli@bootlin.com> wrote:
> >
> > Hi Khem,
> >
> > Il giorno Sat, 7 May 2022 17:38:20 -0700
> > "Khem Raj" <raj.khem@gmail.com> ha scritto:
> >
> > > Major gcc release with lot of changes [2]
> > >
> > > - Add patch to re-shuffle include of sched.h to fix build on musl
> > > - porting guide to gcc 12 [1]
> > > - Fix version in maintainers entry
> > >
> > > [1] https://gcc.gnu.org/gcc-12/porting_to.html
> > > [2] https://gcc.gnu.org/gcc-12/changes.html
> > >
> > > Signed-off-by: Khem Raj <raj.khem@gmail.com>
> >
> > We have a xen-tools build failure on meta-virt with this patch
> > applied:
> >
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/128/builds/60/steps/13/logs/stdio
> >
> > and the same build succeeds without that patch:
> >
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/128/builds/61/steps/13/logs/stdio
> >
>
> yeah this has been taken care in meta-virtualization/master this
> morning. So please give it another
> spin.
Indeed it succeeded now:
https://autobuilder.yoctoproject.org/typhoon/#/builders/128/builds/65
Thank you!
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2022-05-10 10:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-08 0:38 [PATCH] gcc: upgrade 11.3 -> 12.1 Khem Raj
2022-05-09 21:39 ` [OE-core] " Luca Ceresoli
2022-05-09 23:59 ` Khem Raj
2022-05-10 10:37 ` Luca Ceresoli [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=20220510123718.451b33ef@melee \
--to=luca.ceresoli@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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