All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
	openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] gcc12 testing results
Date: Mon, 9 May 2022 08:27:06 -0700	[thread overview]
Message-ID: <CAMKF1sontKL6cGgcCSxxo3WmKU7jeDWDKkT+WChBjduweezH0Q@mail.gmail.com> (raw)
In-Reply-To: <CADkTA4MuiKGp-PqEC2B4UmsiUrVi89kTxm_Bn9=-myOGsoWo_A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1600 bytes --]

On Mon, May 9, 2022 at 6:24 AM Bruce Ashfield <bruce.ashfield@gmail.com>
wrote:

> On Fri, May 6, 2022 at 11:14 AM Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> >
> > I reran the gcc 12 testing. We still have an issue with linux-yocto
> > 5.10 and edgerouter:
> >
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/111/builds/3046
>
> I just sent the yocto-bsp bump to 5.10.113, which had the identified
> -stable fix for gcc12. I can't say it is 100% complete at runtime for
> gcc12, but this moves us along.
>
> >
> > and meta-virtualization has a couple of issues:
> >
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/128/builds/46
> >
>
> I pushed the patch that Ross found on opensuse for gcc12 and Xen. I
> can only say that it doesn't break gcc11 at the moment, but again, it
> moves us along.


Thanks I will test it locally as well since I have xen workspace handy atm

>
>
> Bruce
>
> > Build is still going.
> >
> > Cheers,
> >
> > Richard
> >
> > -=-=-=-=-=-=-=-=-=-=-=-
> > Links: You receive all messages sent to this group.
> > View/Reply Online (#165340):
> https://lists.openembedded.org/g/openembedded-core/message/165340
> > Mute This Topic: https://lists.openembedded.org/mt/90935511/1050810
> > Group Owner: openembedded-core+owner@lists.openembedded.org
> > Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [
> bruce.ashfield@gmail.com]
> > -=-=-=-=-=-=-=-=-=-=-=-
> >
>
>
> --
> - Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end
> - "Use the force Harry" - Gandalf, Star Trek II
>

[-- Attachment #2: Type: text/html, Size: 3042 bytes --]

  reply	other threads:[~2022-05-09 15:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-06 15:14 gcc12 testing results richard.purdie
2022-05-06 15:41 ` Khem Raj
2022-05-06 16:08   ` Bruce Ashfield
2022-05-07  4:46     ` Khem Raj
2022-05-09 11:51     ` [OE-core] " Ross Burton
2022-05-07  4:42 ` Khem Raj
2022-05-08  7:51   ` richard.purdie
2022-05-09 13:24 ` [OE-core] " Bruce Ashfield
2022-05-09 15:27   ` Khem Raj [this message]
2022-05-09 16:34   ` richard.purdie
2022-05-09 16:52     ` Khem Raj

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=CAMKF1sontKL6cGgcCSxxo3WmKU7jeDWDKkT+WChBjduweezH0Q@mail.gmail.com \
    --to=raj.khem@gmail.com \
    --cc=bruce.ashfield@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    /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.