From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Wed, 22 Jul 2015 22:06:06 +0200 Subject: [Buildroot] Analysis of build failures In-Reply-To: <55AFB950.10603@zacarias.com.ar> References: <20150722063018.99E6B101957@stock.ovh.net> <20150722094349.424e7a3e@free-electrons.com> <55AF8CF6.7080709@zacarias.com.ar> <20150722144535.103766f3@free-electrons.com> <55AF91B5.8050806@zacarias.com.ar> <20150722165405.217f4e4f@free-electrons.com> <55AFB950.10603@zacarias.com.ar> Message-ID: <20150722220606.58233cd0@free-electrons.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Gustavo, On Wed, 22 Jul 2015 12:40:00 -0300, Gustavo Zacarias wrote: > It's been a long time since i touched SPARC hardware, and even so i > think this looks like the right approach. > Though for other packages we'll still need to handle the libatomic > situation on a per-arch basis, but it will need to be finer-grained than > that since different ISA levels affect the availability of atomics as well. Let's have a look at the issue on a per-package basis. For webkit, can it either avoid using atomic operations (like glib), or can we add a configure.ac test for the availability of the atomic operations, and if not available, attempt again with -latomic linked in? Thanks, Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com