From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/mpd: disable on SPARCV8, NIOS2, ARMV{4, 5}
Date: Sun, 22 Jan 2017 17:26:00 +1100 [thread overview]
Message-ID: <20170122172600.333588cf@free-electrons.com> (raw)
In-Reply-To: <20170121161100.3142-1-joerg.krause@embedded.rocks>
Hello,
On Sat, 21 Jan 2017 17:11:00 +0100, J?rg Krause wrote:
> Since version 0.20 mpd uses the C++11 feature `std::exception_ptr` which
> is not available on architectures that do not have always-lock-free
> atomics for int.
>
> The issue [1,2] has been fixed in GCC trunk r244051 [3] and will be
> available in GCC 7. However, as GCC 7 is not released yet and will not
> be before the next release of Buildroot, we disable the following
> architectures, which caused build errors on the autobuilders:
> * SPARCV8
> * NIOS2
> * ARMV4
> * ARMV5
>
> Fixes:
> http://autobuild.buildroot.net/results/1c5/1c5090fe361b08c60277e54be1bfa7e80d5d31d8/
> http://autobuild.buildroot.net/results/076/07621b958a3a35066790543586549aa41f2effa9/
> http://autobuild.buildroot.net/results/7b1/7b12d41bee83ad20251dbc7026e0fc665d5abe0c/
> .. and many more
How many packages are potentially affected by this?
The reason I'm asking is because I believe a
BR2_TOOLCHAIN_HAS_GCC_BUG_xyz hidden option would be a bit better:
1. It would document what this is for
2. It would avoid repeating the architecture conditions
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-01-22 6:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-21 16:11 [Buildroot] [PATCH] package/mpd: disable on SPARCV8, NIOS2, ARMV{4, 5} Jörg Krause
2017-01-22 6:26 ` Thomas Petazzoni [this message]
2017-01-22 10:19 ` Jörg Krause
2017-01-30 9:49 ` Thomas Petazzoni
2017-01-30 19:55 ` Jörg Krause
2017-01-30 20:27 ` 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=20170122172600.333588cf@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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