From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: bero@lindev.ch, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] gcc 12 support
Date: Sat, 19 Mar 2022 16:49:40 +0000 [thread overview]
Message-ID: <04644aafdf57575658af21571bc20161d603dca7.camel@linuxfoundation.org> (raw)
In-Reply-To: <2a0122-6235d000-5-7996a200@202814967>
On Sat, 2022-03-19 at 13:44 +0100, Bernhard Rosenkränzer via
lists.openembedded.org wrote:
> with gcc 12 likely being released next month, I thought it's a good idea to
> get started on supporting it -- I've submitted a patch that fixes building
> ovmf, will submit a few more as I run into more failures.
Please do, these are things we're going to have to deal with sooner or later so
good to get started on them!
> If anyone is interested in gcc 12 itself, I've uploaded a recipe for the
> current 12 snapshot to https://lindev.ch/gcc12.tar.xz
> (Probably not worth submitting until gcc 12 is released upstream...)
Handy to know it is there, thanks!
Cheers,
Richard
next prev parent reply other threads:[~2022-03-19 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-19 12:44 gcc 12 support Bernhard Rosenkraenzer
2022-03-19 16:49 ` Richard Purdie [this message]
2022-03-19 19:06 ` [OE-core] " 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=04644aafdf57575658af21571bc20161d603dca7.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bero@lindev.ch \
--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 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.