diff options
author | Thomas Petazzoni <thomas.petazzoni@free-electrons.com> | 2016-02-02 16:31:29 +0100 |
---|---|---|
committer | Thomas Petazzoni <thomas.petazzoni@free-electrons.com> | 2016-02-06 11:16:00 +0100 |
commit | 55dc90db2ea14af1b36d858de2f89b71484f2aa5 (patch) | |
tree | bb245dc5512912689d0191cd898927eb585433f1 /package/python-msgpack | |
parent | e64573c47faa4c60d2c331a3f3d677b89b096a29 (diff) | |
download | buildroot-55dc90db2ea14af1b36d858de2f89b71484f2aa5.tar.gz buildroot-55dc90db2ea14af1b36d858de2f89b71484f2aa5.zip |
squid: rework atomic handling
squid can use the __sync built-ins when available, but uses an
AC_TRY_RUN autoconf tests to check their availability, which isn't
compatible with cross-compilation. Due to this, squid.mk is already
hinting the configure script about this by passing
squid_cv_gnu_atomics=yes/no depending on the availability of atomic
operations.
So far, squid.mk was assuming that BR2_ARCH_HAS_ATOMICS &&
BR2_ARCH_IS_64 was needed, since 8 bytes __sync built-ins are
used. However, this was a bit too restrictive, since certain 32 bits
architectures (ARM, x86) do provide 8 bytes __sync built-ins.
So, instead of using BR2_ARCH_HAS_ATOMICS, we now rely on
BR2_TOOLCHAIN_HAS_SYNC_4 and BR2_TOOLCHAIN_HAS_SYNC_8, since both 4
bytes and 8 bytes __sync built-ins are tested by the autoconf test.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Diffstat (limited to 'package/python-msgpack')
0 files changed, 0 insertions, 0 deletions