From: "akuster" <akuster808@gmail.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
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 14:20:03 -0800 [thread overview]
Message-ID: <bda3e653-f49f-6464-c47e-48b58c89d07d@gmail.com> (raw)
In-Reply-To: <ca75402e-b19-4796-ff75-4769e628ea2e@crashcourse.ca>
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?
-armin
> rday
>
>
>
next prev parent reply other threads:[~2021-02-15 22:22 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 ` akuster [this message]
2021-02-15 22:27 ` [OE-core] " Robert P. J. Day
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=bda3e653-f49f-6464-c47e-48b58c89d07d@gmail.com \
--to=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=rpjday@crashcourse.ca \
/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