All of lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] mpd: disable for sparcv8
Date: Tue, 19 Jan 2016 23:43:38 +0100	[thread overview]
Message-ID: <20160119224338.GA16884@waldemar-brodkorb.de> (raw)

Even the main source code in mpd requires some missing
atomic ops. So only disable some failing plugins, does not
solve the following autobuild error:
http://autobuild.buildroot.net/results/e2207280f3a177e12dba502b1c01f5aeb431d04c/

Leon3 works fine.

Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
---
 package/mpd/Config.in |    2 ++
 1 file changed, 2 insertions(+)

diff --git a/package/mpd/Config.in b/package/mpd/Config.in
index be0843f..b88c0ca 100644
--- a/package/mpd/Config.in
+++ b/package/mpd/Config.in
@@ -6,6 +6,7 @@ menuconfig BR2_PACKAGE_MPD
 	depends on BR2_USE_MMU # libglib2
 	depends on BR2_TOOLCHAIN_GCC_AT_LEAST_4_6
 	depends on BR2_PACKAGE_BOOST_ARCH_SUPPORTS
+	depends on !BR2_sparc_v8 # feature need atomic ops
 	select BR2_PACKAGE_BOOST
 	select BR2_PACKAGE_LIBGLIB2
 	select BR2_PACKAGE_LIBICONV if !BR2_ENABLE_LOCALE
@@ -303,6 +304,7 @@ config BR2_PACKAGE_MPD_UPNP
 endif
 
 comment "mpd needs a toolchain w/ C++, threads, wchar, gcc >= 4.6"
+	depends on !BR2_sparc_v8 # feature need atomic ops
 	depends on BR2_USE_MMU
 	depends on BR2_PACKAGE_BOOST_ARCH_SUPPORTS
 	depends on !BR2_INSTALL_LIBSTDCPP || !BR2_USE_WCHAR || \
-- 
1.7.10.4

             reply	other threads:[~2016-01-19 22:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-19 22:43 Waldemar Brodkorb [this message]
2016-01-20  9:18 ` [Buildroot] [PATCH] mpd: disable for sparcv8 Thomas Petazzoni
2016-01-22 17:46   ` Waldemar Brodkorb
2016-01-22 18:06     ` Thomas Petazzoni
2016-02-07 21:04 ` 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=20160119224338.GA16884@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 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.