From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] strongswan: needs atomics
Date: Wed, 08 Apr 2015 17:19:09 -0300 [thread overview]
Message-ID: <55258D3D.9070800@zacarias.com.ar> (raw)
In-Reply-To: <20150408212227.615c05a2@free-electrons.com>
On 04/08/2015 04:22 PM, Thomas Petazzoni wrote:
> Hum, I don't quite see how this change can fix the build issue. The
> build issue is on Microblaze, and Microblaze has BR2_ARCH_HAS_ATOMICS=y.
>
> So while I agree that Strongswan is indeed using atomic intrinsics, it
> isn't going to fix the issue.
The real problem is that we declared that microblaze has atomics when it
doesn't. All of the __atomic_compare_and_exchange_? functions for
microblaze live in libatomic, which is a clear indication that it has no
native atomics support whatsoever.
Regards.
next prev parent reply other threads:[~2015-04-08 20:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 15:32 [Buildroot] [PATCH] strongswan: needs atomics Gustavo Zacarias
2015-04-08 19:22 ` Thomas Petazzoni
2015-04-08 20:19 ` Gustavo Zacarias [this message]
2015-04-08 20:40 ` Thomas Petazzoni
2015-04-08 21:15 ` Gustavo Zacarias
2015-04-08 21:22 ` Thomas Petazzoni
2015-04-08 21:25 ` Gustavo Zacarias
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=55258D3D.9070800@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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