From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] utils/genrandconfig: filter microblaze GCC < 8 bug
Date: Fri, 25 May 2018 08:13:30 +0200 [thread overview]
Message-ID: <20180525081330.270d00e7@windsurf> (raw)
In-Reply-To: <CANQCQpZfqWK4zaq_4hUZkzhX2WvdWwKGzRKsXPJ0NhubWQDfng@mail.gmail.com>
Hello,
On Thu, 24 May 2018 22:49:07 -0500, Matthew Weber wrote:
> Looks like it doesn't really matter what you enable/disable for boost
> options as it's when the bjam tool is getting called that it gets
> stuck. I can start to look at all the reverse dependencies
> tomorrow....
bjam is Boost's build tool, so obviously it fails within a bjam
invocation. But basically, you can just try to do a minimal Boost
build, with no sub-option enabled. If that still triggers the infinite
loop with Microblaze gcc, then we don't have any other choice but to
add the BR2_TOOLCHAIN_GCC_HAS_BUG_xyz dependency on BR2_PACKAGE_BOOST
itself, and propagate it to the reverse dependencies.
Have you tried playing around with optimization levels, and see if they
all trigger this issue ? For example instead of using -Os, does the
issue also appear at -O2 ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-05-25 6:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 21:53 [Buildroot] [PATCH] utils/genrandconfig: filter microblaze GCC < 8 bug Matt Weber
2018-05-23 22:20 ` Arnout Vandecappelle
2018-05-24 11:30 ` Thomas Petazzoni
2018-05-25 3:14 ` Matthew Weber
2018-05-25 3:49 ` Matthew Weber
2018-05-25 6:13 ` Thomas Petazzoni [this message]
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=20180525081330.270d00e7@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.