From: "Jacob Kroon" <jacob.kroon@gmail.com>
To: 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, 5 Aug 2020 07:05:44 +0200 [thread overview]
Message-ID: <9e59ca1e-26f3-08a2-d43d-c4d4545d031a@gmail.com> (raw)
In-Reply-To: <CAMKF1soyMVB0jpLRA0v8WnCMaJ8DHf=id0xyvdoJ+78CL=UKwA@mail.gmail.com>
On 8/5/20 2:14 AM, Khem Raj wrote:
> On Tue, Aug 4, 2020 at 1:20 AM Jacob Kroon <jacob.kroon@gmail.com> wrote:
>>
>> It has been almost 3 months since the upgrade to gcc 10. Switch back to
>> relying on gcc default configuration (-fno-common).
>>
>
> have you done a world build with this? In core+meta-oe I still see 70+
> recipes failing
> what will be good is if people start sending fixes before switching
> the defaults.
>
Ah, that I haven't, only the images I use. Is there a list of failing
recipes available somewhere ?
Jacob
next prev parent reply other threads:[~2020-08-05 5:05 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 [this message]
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
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=9e59ca1e-26f3-08a2-d43d-c4d4545d031a@gmail.com \
--to=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