Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2015-11-18
Date: Sun, 22 Nov 2015 08:53:31 +0100	[thread overview]
Message-ID: <20151122075330.GP19876@waldemar-brodkorb.de> (raw)
In-Reply-To: <564F3C6D.8080502@zacarias.com.ar>

Hi Gustavo,
Gustavo Zacarias wrote,

> On 19/11/15 20:15, Thomas Petazzoni wrote:
> This is in the bag of "arch needs libatomic" together with
> strongswan for microblaze.
> 
> >>sparc |                    mpd-0.19.11 | NOK | http://autobuild.buildroot.net/results/8dcf5f73904de835bf66c46747cd544efc9d3a22/
> >
> >undefined reference to `__atomic_fetch_or_4'
> >
> >Waldemar, can you have a look ?
> 
> SPARC (v8, 32 bits) doesn't have atomics at all, libatomic, again
> could fit the bill. It may be inherited from somewhere else like
> boost.

Can you explain this? I can't see any special handling for boost and
atomics in buildroot. Or do you mean how boost handle it atomic
implementation for sparc?

best regards
 Waldemar

  parent reply	other threads:[~2015-11-22  7:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-19  7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2015-11-18 Thomas Petazzoni
2015-11-19 23:15 ` [Buildroot] Analysis of build " Thomas Petazzoni
2015-11-20  0:17   ` Ryan Barnett
2015-11-20 15:29   ` Gustavo Zacarias
2015-11-20 15:45     ` Thomas Petazzoni
2015-11-22  7:53     ` Waldemar Brodkorb [this message]
2015-11-20 21:01   ` Alexey Brodkin
2015-11-24 12:10     ` Alexey Brodkin
2015-11-20 22:26   ` Arnout Vandecappelle
2015-11-21  8:23     ` Thomas Petazzoni
2015-11-21 21:14       ` Arnout Vandecappelle
2015-11-21 14:45   ` Martin Bark
2015-11-21 22:17     ` Arnout Vandecappelle
2015-11-22 18:31       ` Martin Bark
2015-11-23  6:22   ` Rodrigo Rebello

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=20151122075330.GP19876@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