From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] openal: Explicitly enable/disable NEON support to avoid trouble with precompiled toolchains
Date: Sun, 28 Aug 2016 15:50:06 +0200 [thread overview]
Message-ID: <20160828155006.0abb2572@free-electrons.com> (raw)
In-Reply-To: <1472387820-6783-1-git-send-email-nerv@dawncrow.de>
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@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
next prev parent reply other threads:[~2016-08-28 13:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-28 12:37 [Buildroot] [PATCH] openal: Explicitly enable/disable NEON support to avoid trouble with precompiled toolchains André Hentschel
2016-08-28 13:50 ` Thomas Petazzoni [this message]
2016-08-28 14:10 ` André Hentschel
2016-08-31 23:13 ` Arnout Vandecappelle
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=20160828155006.0abb2572@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.