All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andrea Adami" <andrea.adami@gmail.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: RFC: pulseaudio vs. meson vs. neon
Date: Mon, 28 Jun 2021 12:01:55 +0200	[thread overview]
Message-ID: <CAAQYJAvFsFr-1WDMkqeSLReq6V2irGR04XOEoVa_GnXAK+abqA@mail.gmail.com> (raw)

Hello,

during a core-image-sato build for armv4 I got one single build
failure with pulseaudio.

This happens after commit 80bbea0 pulseaudio: switch build system from
Autotools to Meson. In the commit text it is evidenced:

"
With Meson there's no option for disabling Neon optimizations if the
compiler supports Neon. If -mfpu is set in CC or CFLAGS, it's ignored,
because the build system adds -mfpu=neon at the end of the compiler
command line, overriding any earlier -mfpu options. This shouldn't be
a problem, because PulseAudio detects at runtime whether the CPU
supports Neon instructions.
"

At the moment to build pulseaudio for armv4/5 I have reverted to using
autotools.


There was around a patch but has not been merged.
https://lists.openembedded.org/g/openembedded-core/message/146375

Maybe a v2 will be accepted?

Cheers
A.A.

             reply	other threads:[~2021-06-28 10:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-28 10:01 Andrea Adami [this message]
2021-06-28 10:59 ` [OE-core] RFC: pulseaudio vs. meson vs. neon Alexander Kanavin
2021-06-28 12:08   ` Andrea Adami
2021-06-28 12:36     ` Alexander Kanavin
2021-06-28 12:44       ` Andrea Adami
2021-06-28 13:03         ` Richard Purdie
2021-06-28 13:10           ` Andrea Adami
2021-06-28 17:55 ` Khem Raj
2021-06-28 18:20   ` Andrea Adami
2021-06-28 18:46     ` Khem Raj
2021-06-28 19:10       ` Phil Blundell
2021-06-28 19:42         ` Khem Raj
2021-06-28 19:52           ` Phil Blundell
2021-06-28 21:10             ` Khem Raj
2021-06-28 21:21               ` Phil Blundell
2021-06-28 21:40                 ` Khem Raj

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=CAAQYJAvFsFr-1WDMkqeSLReq6V2irGR04XOEoVa_GnXAK+abqA@mail.gmail.com \
    --to=andrea.adami@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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.