[Buildroot] [PATCH] openal: Explicitly enable/disable NEON support to avoid trouble with precompiled toolchains

Thomas Petazzoni thomas.petazzoni at free-electrons.com
Sun Aug 28 13:50:06 UTC 2016


Hello,

Why do you think the problem is with "precompiled" toolchains only?

On Sun, 28 Aug 2016 14:37:00 +0200, André Hentschel wrote:
> Fixes:
> http://autobuild.buildroot.net/results/d7ccef77a355ccc23f26d012e8441af931469ae4
> http://autobuild.buildroot.net/results/b5777a0ed33f6bb7a5fc0486ea21ecef58615dac
> Signed-off-by: André Hentschel <nerv at dawncrow.de>
> ---
>  package/openal/openal.mk | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/package/openal/openal.mk b/package/openal/openal.mk
> index 2916aa6..8205f9e 100644
> --- a/package/openal/openal.mk
> +++ b/package/openal/openal.mk
> @@ -50,4 +50,11 @@ ifeq ($(BR2_STATIC_LIBS),y)
>  OPENAL_CONF_OPTS += -DLIBTYPE=STATIC
>  endif
>  
> +# Explicitly enable/disable NEON support to avoid trouble with precompiled toolchains
> +ifeq ($(BR2_ARM_FPU_NEON)$(BR2_ARM_FPU_NEON_VFPV4),y)

I believe you should use BR2_ARM_CPU_HAS_NEON instead.

Thanks!

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



More information about the buildroot mailing list