From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Jacob Kroon <jacob.kroon@gmail.com>, Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] gcc10: Don't default back to -fcommon
Date: Wed, 05 Aug 2020 14:26:14 +0100 [thread overview]
Message-ID: <a4222506e98bfa3c11f4b14517f4092b951d81a8.camel@linuxfoundation.org> (raw)
In-Reply-To: <3237f09f-7b55-97b2-9c39-8bc7bf1a62c9@gmail.com>
On Wed, 2020-08-05 at 15:15 +0200, Jacob Kroon wrote:
> On 8/5/20 8:17 AM, Khem Raj wrote:
> > here is a recent build with clang11 which also switched to using
> > -fno-common and errors are pretty much same you will see with gcc10
> > with this patch to revert the -fcommon defaults.
> >
> > https://errors.yoctoproject.org/Errors/Build/107234/?limit=100
> >
> > I was waiting for upstream packages to get fixed before switching
> > the
> > defaults back to -fno-common.
> >
>
> Yes I understand, maybe its better to hold this for now.
>
> Having a list of recipes that needs fixing would probably speed
> things up. I can have a look at some of them.
I ran this through with just OE-Core and the list of failures is:
https://autobuilder.yoctoproject.org/typhoon/#/builders/52/builds/2237
I'm a little frustrated that patches like this get sent and them people
like Khem and I have to spot and avoid the problems as there isn't
testing :/.
I'll drop the patch for now until more of these issues are resolved.
Cheers,
Richard
next prev parent reply other threads:[~2020-08-05 13:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 8:20 [PATCH] gcc10: Don't default back to -fcommon Jacob Kroon
2020-08-05 0:14 ` [OE-core] " Khem Raj
2020-08-05 5:05 ` Jacob Kroon
2020-08-05 6:00 ` Khem Raj
2020-08-05 6:17 ` Khem Raj
2020-08-05 13:15 ` Jacob Kroon
2020-08-05 13:26 ` Richard Purdie [this message]
2020-08-15 22:10 ` Richard Purdie
2020-08-16 1:56 ` Khem Raj
2020-08-16 2:41 ` Khem Raj
2020-08-16 13:47 ` Richard Purdie
2020-08-16 22:55 ` Bruce Ashfield
2020-08-16 23:14 ` Khem Raj
2020-08-17 12:27 ` Richard Purdie
2020-08-17 14:15 ` Bruce Ashfield
2020-08-17 14:45 ` Richard Purdie
2020-08-17 19:47 ` Khem Raj
2020-08-17 19:55 ` Khem Raj
2020-08-17 21:07 ` Bruce Ashfield
2020-08-18 11:57 ` Martin Jansa
2020-08-18 12:21 ` Bruce Ashfield
2020-08-18 16:03 ` Martin Jansa
2020-08-18 16:34 ` Khem Raj
2020-08-18 17:05 ` Bruce Ashfield
2020-08-16 23:29 ` 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=a4222506e98bfa3c11f4b14517f4092b951d81a8.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=jacob.kroon@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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