From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain: GCC bug 85862
Date: Wed, 23 May 2018 23:08:10 +0200 [thread overview]
Message-ID: <e1330fb2-8262-d2c9-433d-d3d22b574f72@gmail.com> (raw)
In-Reply-To: <CANQCQpbT7m4H6gFjPg5BNssOzUqHsBQRnNpDhH_y5t3-x-gS0g@mail.gmail.com>
Hi Matt,
Le 23/05/2018 ? 22:57, Matthew Weber a ?crit?:
> Romain,
>
> On Wed, May 23, 2018 at 3:38 PM, Romain Naour <romain.naour@gmail.com> wrote:
>>
>> Hi Thomas,
>>
>> Le 22/05/2018 ? 23:00, Thomas Petazzoni a ?crit :
>>> Hello,
>>>
>>> On Mon, 21 May 2018 15:29:42 -0500, Matt Weber wrote:
>>>> GCC < 7.x hangs while building libnss for the Microblaze Arch.
>>>>
>>>> Discovered by
>>>> http://autobuild.buildroot.net/results/158e8ebb39713e1b436a5cc1a1916f46c30694df
>>>>
>>>> Reported:
>>>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85862
>>
>> This bug has been marked as a duclicate of the bug I identified.
>>
>>>>
>>>> Simlar to:
>>>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49218
>>>>
>>>> Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com>
>>>
>>> Beyond the libnss issue, we do have at least three other Microblaze timeouts. However, I think Romain Naour had identified a different issue for those:
>>>
>>> http://autobuild.buildroot.net/?status=TIMEOUT&arch=microblazeel
>>>
>>> Affected packages: flare-engine, boost, gst-ffmpeg.
>>
>> We can mark these packages affected by bug 85852 or 85180.
>>
>
> Any proposed ways to impl other then adding another BR2_TOOLCHAIN_HAS_GCC_BUG_*
We can add an autobuilder exception to reject configs building these packages
with a microblaze toolchain.
Best regards,
Romain
>
> Matt
>
next prev parent reply other threads:[~2018-05-23 21:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 20:29 [Buildroot] [PATCH] toolchain: GCC bug 85862 Matt Weber
2018-05-21 21:49 ` Peter Korsgaard
2018-05-22 21:00 ` Thomas Petazzoni
2018-05-23 20:38 ` Romain Naour
2018-05-23 20:57 ` Matthew Weber
2018-05-23 21:08 ` Romain Naour [this message]
2018-05-23 21:55 ` Matthew Weber
2018-06-07 12:43 ` davidb
2018-06-07 13:11 ` Thomas Petazzoni
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=e1330fb2-8262-d2c9-433d-d3d22b574f72@gmail.com \
--to=romain.naour@gmail.com \
--cc=buildroot@busybox.net \
/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