From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] llvm: add dependency on !BR2_TOOLCHAIN_HAS_GCC_BUG_64735
Date: Fri, 6 Apr 2018 13:37:44 +0200 [thread overview]
Message-ID: <20180406133744.43c8f225@windsurf> (raw)
In-Reply-To: <a8703b32-9442-95d3-4ea6-b008cd791cf8@smile.fr>
Hello,
On Fri, 6 Apr 2018 11:36:26 +0200, Valentin Korenblit wrote:
> The three autotests crashed because of std::shared_future,
>
> I've found the following in: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820535
>
> "This looks like the kind of failure you get when your host toolchain
> doesn't support C++11 properly (specifically lock-free atomics in this
> case). When I've seen it before GCC was defaulting to a CPU that's
> too old to do atomics properly, and that configuration is very
> unlikely to be supported by LLVM ever (any more)."
>
> I was about to send a patch to blacklist ARMv4 and ARMv5 but this should
> be a more appropriate solution (I was not aware of BUG_64735).
Note: I didn't test building LLVM for ARMv4/ARMv5, with a gcc 7.x
compiler. But the build error itself clearly points to this gcc
limitation, which has been solved in gcc 7.x.
> I'll try to build with the defconfigs from the autobuilder applying the
> patch and adding a dependency on !BR2_STATIC_LIBS.
So far, there hasn't been any failure to build LLVM in static only
configurations, so let's see if any shows up.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-04-06 11:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 9:00 [Buildroot] [PATCH 1/2] llvm: add dependency on !BR2_TOOLCHAIN_HAS_GCC_BUG_64735 Thomas Petazzoni
2018-04-06 9:00 ` [Buildroot] [PATCH 2/2] mesa3d: properly propagate the dependencies of BR2_PACKAGE_LLVM Thomas Petazzoni
2018-04-06 9:17 ` Valentin Korenblit
2018-04-06 9:36 ` [Buildroot] [PATCH 1/2] llvm: add dependency on !BR2_TOOLCHAIN_HAS_GCC_BUG_64735 Valentin Korenblit
2018-04-06 11:37 ` Thomas Petazzoni [this message]
2018-04-06 19:31 ` 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=20180406133744.43c8f225@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