From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] m68k: gcc coldfire does not provide _sync atomics
Date: Mon, 13 Jun 2016 08:03:03 +0200 [thread overview]
Message-ID: <20160613060303.GA7896@waldemar-brodkorb.de> (raw)
Trying to use __sync_fetch_and_add ends with a gcc ICE.
This fixes following autobuild failure, by actually disabling
the package for coldfire:
http://autobuild.buildroot.net/results/d719db11210d42501332586b4485ab0cc1e125dd/
Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
---
toolchain/toolchain-common.in | 2 ++
1 file changed, 2 insertions(+)
diff --git a/toolchain/toolchain-common.in b/toolchain/toolchain-common.in
index 1fe28a9..847c905 100644
--- a/toolchain/toolchain-common.in
+++ b/toolchain/toolchain-common.in
@@ -331,6 +331,7 @@ config BR2_TOOLCHAIN_HAS_SYNC_1
bool
default y
depends on !BR2_bfin
+ depends on !BR2_m68k_cf
depends on !BR2_microblaze
depends on !BR2_sparc
depends on !(BR2_arc && !BR2_ARC_ATOMIC_EXT)
@@ -342,6 +343,7 @@ config BR2_TOOLCHAIN_HAS_SYNC_2
config BR2_TOOLCHAIN_HAS_SYNC_4
bool
default y
+ depends on !BR2_m68k_cf
depends on !BR2_sparc
depends on !(BR2_arc && !BR2_ARC_ATOMIC_EXT)
--
2.1.4
next reply other threads:[~2016-06-13 6:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 6:03 Waldemar Brodkorb [this message]
2016-06-27 13:06 ` [Buildroot] [PATCH] m68k: gcc coldfire does not provide _sync atomics Peter Korsgaard
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=20160613060303.GA7896@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--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