Bug#1087828: openal-soft: FTBFS on ppc64el: error: ‘tmp’ was not declared in this scope

[Simon McVittie]

Control: forwarded -1 https://github.com/kcat/openal-soft/issues/1061

On Tue, 19 Nov 2024 at 09:33:52 +0100, Matthias Klose wrote:
> /<<PKGBUILDDIR>>/common/pffft.cpp: In function ‘void
> {anonymous}::uninterleave2(v4sf, v4sf, v4sf&, v4sf&)’:
...
> /<<PKGBUILDDIR>>/common/pffft.cpp:130:12: error: ‘tmp’ was not declared in
> this scope; did you mean ‘tm’?
>   130 |     out1 = tmp;

This looks like the Altivec code path is just wrong, and has most likely
never actually been tested (it seems unlikely that upstream has a POWER
machine available). Perhaps a PowerPC enthusiast could fix and test this
code path, and send a tested PR?

Building with -DPFFFT_SIMD_DISABLE on ppc64el would probably work
as a shorter-term workaround for this.

    smcv