From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Jon Mason <jdmason@kudzu.us>
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: Sat, 27 May 2023 16:00:27 +0100 [thread overview]
Message-ID: <cf01812048cf651b022875996442e5d2ead18e95.camel@linuxfoundation.org> (raw)
In-Reply-To: <ZHEhlRXG8GHFCeaS@kudzu.us>
On Fri, 2023-05-26 at 17:16 -0400, Jon Mason wrote:
> 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, that resolved that issue but allowed another to show through:
https://autobuilder.yoctoproject.org/typhoon/#/builders/113/builds/4040/steps/12/logs/stdio
in the 6.1 kernel.
Which might be fixed with:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/scripts/gcc-plugins?id=e6a71160cc145e18ab45195abf89884112e02dfb
or perhaps:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/scripts/gcc-plugins?id=5a6b64adc18d9adfb497a529ff004d59b6df151f
Are you using up to date SRCREVs for 6.1?
Cheers,
Richard
prev parent reply other threads:[~2023-05-27 15:00 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
2023-05-27 15:00 ` Richard Purdie [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=cf01812048cf651b022875996442e5d2ead18e95.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Jon.Mason@arm.com \
--cc=alexandre.belloni@bootlin.com \
--cc=anuj.mittal@intel.com \
--cc=bruce.ashfield@gmail.com \
--cc=jdmason@kudzu.us \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox