What I am saying is, can you discuss this with upstream first please?

Alex

On Mon, 28 Jun 2021 at 14:08, Andrea Adami [off-list ref] wrote:

On Mon, Jun 28, 2021 at 1:00 PM Alexander Kanavin
[off-list ref] wrote:

quoted

Seems like an upstream problem rather than a Yocto one?

Indeed,

from
https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/14.0/
"
One difference from Autotools is that the --disable-neon-opt option
for disabling NEON optimizations doesn't have a counterpart in Meson
due to how Meson's NEON detection works. NEON will always be enabled
if the compiler supports it, but even if the target machine doesn't
support NEON, that shouldn't be a problem, because PulseAudio disables
NEON at run-time if the processor doesn't support it.
"
Upstream *thinks* this is not an issue because all will be fine at runtime
:)

Cheers
A.A:

quoted

Alex

On Mon, 28 Jun 2021 at 12:02, Andrea Adami [off-list ref]

wrote:

quoted

quoted

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.