From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: akuster808 <akuster808@gmail.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] upgrading pseudo on zeus branch to handle gcc 10?
Date: Mon, 15 Feb 2021 17:27:34 -0500 (EST) [thread overview]
Message-ID: <19969497-5e8a-cf53-1533-159e40f87d51@crashcourse.ca> (raw)
In-Reply-To: <bda3e653-f49f-6464-c47e-48b58c89d07d@gmail.com>
On Mon, 15 Feb 2021, akuster808 wrote:
>
>
> On 2/15/21 12:11 PM, Robert P. J. Day wrote:
> > yes, i know fedora 33 is not a supported build distro, but in trying
> > an absolutely stock build of core-image-minimal from poky (zeus
> > branch) on my F33 system, i ran into a gcc 10-related build error for
> > which this:
> >
> > https://git.yoctoproject.org/cgit/cgit.cgi/pseudo/commit/?h=oe-core&id=a44361b8d3fbf5fc40cd87b599caeb380454efbe
> >
> > would appear to be just the solution. so is there a proper protocol
> > for handling this? should the zeus branch move up to the incorporate
> > that commit? or what?
> wouldn't bbappend of that patch work?
are you suggesting i just do that locally for my own benefit, or
that that is something that can be submitted as a patch so that others
get the benefit as well? i know i can add that as a local patch, but
if the roadmap includes supporting zeus under gcc 10, then that patch
would need to be applied universally.
rday
prev parent reply other threads:[~2021-02-15 22:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 20:11 upgrading pseudo on zeus branch to handle gcc 10? Robert P. J. Day
2021-02-15 22:20 ` [OE-core] " akuster
2021-02-15 22:27 ` Robert P. J. Day [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=19969497-5e8a-cf53-1533-159e40f87d51@crashcourse.ca \
--to=rpjday@crashcourse.ca \
--cc=akuster808@gmail.com \
--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.