[Buildroot] [PATCH] strongswan: needs atomics

Thomas Petazzoni thomas.petazzoni at free-electrons.com
Wed Apr 8 21:22:30 UTC 2015


Dear Gustavo Zacarias,

On Wed, 08 Apr 2015 18:15:51 -0300, Gustavo Zacarias wrote:

> I'd venture to say the first (hardware has atomics) - that's what it
> means right now because:
> 
> 1) We don't handle libatomic, which is the fallback if HW doesn't do it.
> This would entail adding LIBS="-latomic" for autotools packages, and
> things are magically fixed.
> 
> 2) We don't copy libatomic (patches sent), so we can't do 1 just yet.
> 
> So basically we should rename the whole thing.
> BR2_ARCH_HAS_ATOMICS isn't precise, we need to formulate this probably
> as BR2_ARCH_NEEDS_LIBATOMIC since AFAIK the fallback is mandatory, while
> copying it for the toolchains.
> We could have BR2_TOOLCHAIN_HAS_ATOMICS to point towards
> toolchains/architectures that don't provide atomics and a fallback.
> It also means that packages that were previously excluded can, in fact,
> be used anyway as long as libatomic is thrown to the mix.

Thanks for the summary.

How do you handle Blackfin, which uses gcc 4.3, while I believe
libatomic is a new thing in gcc 4.8, no?

Are you sure all atomic intrinsics are tied to the existence of
libatomic? It's quite hard to find some good documentation on the web
about libatomic.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com



More information about the buildroot mailing list