From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain: GCC bug 85862
Date: Tue, 22 May 2018 23:00:33 +0200 [thread overview]
Message-ID: <20180522230033.0daffecb@windsurf> (raw)
In-Reply-To: <1526934582-53824-1-git-send-email-matthew.weber@rockwellcollins.com>
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
>
> 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.
Romain, Matt, would it be possible to make progress with those timeouts
as well ?
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-05-22 21:00 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 [this message]
2018-05-23 20:38 ` Romain Naour
2018-05-23 20:57 ` Matthew Weber
2018-05-23 21:08 ` Romain Naour
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=20180522230033.0daffecb@windsurf \
--to=thomas.petazzoni@bootlin.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