On Mon, Jun 28, 2021 at 2:36 PM Alexander Kanavin <alex.kana...@gmail.com> wrote: > > What I am saying is, can you discuss this with upstream first please?
Sorry, no, I'm not in the position to do that. Besides, I am dispatching my armv4/armv5te Zaurus hardware so I will not be able to test anymore. My point here is, for this pulseaudio 14.x release (in Honister) we could do an effort and patch the damn file. I write this because this is the only failing recipe for core-image-sato for armv4 and this arch is still supported in oe-core (thank you so much Khem). So I'd say as long as armv4 and armv5t are supported we need to patch the recipe. With next pulseaudio 15.x the older arm will maybe lose support, I don't know now. My 2 cents A.A. > > Alex > > On Mon, 28 Jun 2021 at 14:08, Andrea Adami <andrea.ad...@gmail.com> wrote: >> >> On Mon, Jun 28, 2021 at 1:00 PM Alexander Kanavin >> <alex.kana...@gmail.com> wrote: >> > >> > 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: >> >> > >> > Alex >> > >> > On Mon, 28 Jun 2021 at 12:02, Andrea Adami <andrea.ad...@gmail.com> wrote: >> >> >> >> 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. >> >> >> >> >> >>
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#153361): https://lists.openembedded.org/g/openembedded-core/message/153361 Mute This Topic: https://lists.openembedded.org/mt/83841391/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
