From: Jon Mason <jdmason@kudzu.us>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>,
Jon Mason <Jon.Mason@arm.com>,
"Mittal, Anuj" <anuj.mittal@intel.com>,
Bruce Ashfield <bruce.ashfield@gmail.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Subject: Re: gcc 13 merged, meta-arm, meta-intel and meta-virt issues
Date: Fri, 26 May 2023 17:16:05 -0400 [thread overview]
Message-ID: <ZHEhlRXG8GHFCeaS@kudzu.us> (raw)
In-Reply-To: <f7d8cdc485e3d75304bd41931292f0cb76083e14.camel@linuxfoundation.org>
On Fri, May 26, 2023 at 05:28:21PM +0100, Richard Purdie wrote:
> I just wanted to let people know I merged gcc 13 since I think we'd got
> as far as we were going to without the patches landing. I dropped the
> 5.15 kernel and found ways to fix lttng-tools and glib-2.0 ptest
> issues.
>
> This leaves a few failures on the autobuilder in other layers:
>
> meta-arm 5.15 kernel bbappend:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/113/builds/4038/steps/12/logs/stdio
Sorry, I meant to push the fix yesterday. It's in there now.
Thanks,
Jon
>
> meta-intel intel-mediasdk do_compile:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/100/builds/4488/steps/13/logs/stdio
>
> meta-virt xen-tools do_compile:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/128/builds/1691/steps/12/logs/stdio
>
> Hopefully nothing too difficult to resolve.
>
> We're now in the process of a uninative release which will hopefully
> fix some of the other autobuilder failures.
>
> Cheers,
>
> Richard
>
next prev parent reply other threads:[~2023-05-26 21:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 16:28 gcc 13 merged, meta-arm, meta-intel and meta-virt issues Richard Purdie
2023-05-26 17:30 ` [OE-core] " Martin Jansa
2023-05-27 20:51 ` Christopher Clark
2023-05-26 21:16 ` Jon Mason [this message]
2023-05-27 15:00 ` Richard Purdie
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=ZHEhlRXG8GHFCeaS@kudzu.us \
--to=jdmason@kudzu.us \
--cc=Jon.Mason@arm.com \
--cc=alexandre.belloni@bootlin.com \
--cc=anuj.mittal@intel.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.