From: "Adrian Bunk" <bunk@stusta.de>
To: Tanu Kaskinen <tanuk@iki.fi>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] Why disable NEON support in recipes if runtime detection works?
Date: Sun, 19 Jul 2020 12:30:11 +0300 [thread overview]
Message-ID: <20200719093011.GL1229@localhost> (raw)
In-Reply-To: <64ecaddb6eaae1bd569e299ffb03b13081efe50b.camel@iki.fi>
On Sun, Jul 19, 2020 at 12:06:15PM +0300, Tanu Kaskinen wrote:
>...
> I'm currently converting the pulseaudio recipe from Autotools to Meson,
> and the old Autotools build system supports disabling NEON
> optimizations but the Meson build system doesn't. So I'm wondering if I
> should add the missing feature to the Meson build system, or just let
> the runtime detection do its work.
>...
Looking at the git history it seems this was added as a workaround at a
time when the autodetection was buggy and caused build breakage.
Debian also backported commit 0af05213 (build: make ARM NEON check in
configure.ac more strict) to PulseAudio 4.0, which was included in
PulseAudio 5.0.
> Tanu
cu
Adrian
next prev parent reply other threads:[~2020-07-19 9:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-19 9:06 Why disable NEON support in recipes if runtime detection works? Tanu Kaskinen
2020-07-19 9:30 ` Adrian Bunk [this message]
2020-07-19 9:46 ` [OE-core] " Tanu Kaskinen
2020-07-20 22:26 ` Khem Raj
2020-07-26 6:27 ` Tanu Kaskinen
[not found] ` <1625397D9F68474B.26462@lists.openembedded.org>
2020-07-26 7:59 ` Tanu Kaskinen
2020-07-26 14:01 ` Khem Raj
2020-07-27 20:45 ` Andre McCurdy
2020-07-29 13:46 ` Tanu Kaskinen
2020-07-29 22:08 ` Andre McCurdy
2020-08-23 8:53 ` Tanu Kaskinen
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=20200719093011.GL1229@localhost \
--to=bunk@stusta.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=tanuk@iki.fi \
/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.