Re: Bug#1087828: openal-soft: FTBFS on ppc64el: error: ‘tmp’ was not declared in this scope
Control: forwarded -1 https://github.com/kcat/openal-soft/issues/1061
On Tue, 19 Nov 2024 at 09:33:52 +0100, Matthias Klose wrote:
> /<>/common/pffft.cpp: In function ‘void
> {anonymous}::uninterleave2(v4sf, v4sf, v4sf&, v4sf&)’:
...
> /<>/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
Bug#1087831: openal-soft: FTBFS on powerpc|ppc64: assumes that PowerPC machines, toolchains support Altivec
Source: openal-soft
Version: 1.24.0-1
Severity: normal
Tags: upstream
Justification: fails to build from source on non-release architectures
X-Debbugs-Cc: debian-powerpc@lists.debian.org
User: debian-powerpc@lists.debian.org
Usertags: powerpc ppc64
https://buildd.debian.org/status/fetch.php?pkg=openal-soft&arch=powerpc&ver=1%3A1.24.0-1&stamp=1731961701&raw=0
> In file included from /<>/common/pffft.cpp:102:
> /usr/lib/gcc/powerpc-linux-gnu/14/include/altivec.h:34:2: error: #error Use
> the "-maltivec" flag to enable PowerPC AltiVec support
>34 | #error Use the "-maltivec" flag to enable PowerPC AltiVec support
> | ^
> /<>/common/pffft.cpp:103:14: error: ‘__vector’ does not name a
> type; did you mean ‘vector’?
> 103 | using v4sf = vector float;
> | ^~
> /<>/common/pffft.cpp:105:14: error: ‘v4sf’ does not name a type
> 105 | force_inline v4sf vzero() noexcept { return (vector
> float)vec_splat_u8(0); }
> | ^~~~
https://buildd.debian.org/status/fetch.php?pkg=openal-soft&arch=ppc64&ver=1%3A1.24.0-1&stamp=1731960486&raw=0
shows similar symptoms on ppc64.
This could probably be worked around by building with -DPFFFT_SIMD_DISABLE
on the two affected architectures.
I am not interested in powerpc myself (my only powerpc machine is older
than some active Debian contributors, and has been packed up for donation
to a computing history museum) but I'm reporting this bug because it occurs
to me that it would be easy to work around #1087828 and this bug with a
single change, something like this (untested!):
ifneq ($(filter powerpc% ppc%,$(DEB_HOST_ARCH_CPU)),)
export DEB_CPPFLAGS_MAINT_APPEND += -DPFFFT_SIMD_DISABLE
endif
It would be useful if a PowerPC porter could verify this and turn it
into a tested patch.
smcv
Re: What are the current available browser options for debian-ppc64?
Hi, John Paul Adrian Glaubitz wrote: [1]https://github.com/oracle/solaris-userland/tree/master/components/desktop/firefox/patches interesting set... I recognize one: https://github.com/oracle/solaris-userland/blob/master/components/desktop/firefox/patches/firefox-53-sparc-gfx-atomicops.patch I have applied this one in ArcticFox. It won't cause crashes, just bad colors. If you check discussion on bugzilla, it is one examples where "mozilla hates big endian support". An older bug that upstream doesn't wan't properly to fix. Don't fullu understand it, since apparently it is extra done to support BE. I suppose there are swapping problems Riccardo
Re: What are the current available browser options for debian-ppc64?
Hi, Jan Montag wrote: since I just bought a Powermac G5 (powermac11.2) Dual 2 GHz, I'm running Debian 12 SID on it. I also keep trying to compile or install a current browser. Unfortunately this doesn't work for reasons I don't understand. How has this progressed? The current version of Firefox is 132.0.0.2 and still produces the memory access error on my ppc64 Mac. Segmentation fault. Is there anything new to report here? I can definitely try something out with guidance. But I'm not a programmer or even a hacker. Firefox is an uphill battle.. although it promises of course best compatibility. I wonder who the status of midori is. Otherwise you need to go beyond Debian packages: ArcticFox, BrassMonkey, SeaLion. Riccardo
Re: Re: What are the current available browser options for debian-ppc64?
On Mon, Nov 18, 2024 at 03:43:28PM +0100, Jan Montag wrote: > I also keep trying to compile or install a current > browser. Unfortunately this doesn't work for reasons I don't > understand. How has this progressed? The current version of Firefox > is 132.0.0.2 and still produces the memory access error on my ppc64 > Mac. FYI for Firefox on ppc64el there is these patches for Firefox https://www.talospace.com/2024/11/updated-baseline-jit-openpower-patches.html which do not make it work "completely" but make some progress. "Probably" as John Paul Adrian Glaubitz wrote, big-endian will require even more patches/work.
