Hi Otto, On Wed, 2025-04-23 at 13:32 -0700, Otto Kekäläinen wrote: > I reported this to upstream, who is willing to look into it, but have > no sparc64 access. > > Thus I was hoping some of the Debian sparc64 porters could step in and > test a bit, and help upstream, as they seem responsive to fixing > sparc64.
I don't have the time to go through this whole bug report now, but FYI there is a very fast sparc64 (SPARC M8 clocked at 5 GHz) machine available running Solaris 11.4 in the GCC Compile Farm for which any open source developer can request an account for, see: - https://gcc.gnu.org/wiki/CompileFarm - https://portal.cfarm.net/machines/list/ We also have a sparc64 machine there running Debian unstable, but it's currently offline due to CPU problems. However, we have now finally purchased replacement CPUs and we are confident to get the machine back online soon. If upstream is really willing to work on sparc64 and they want to get the bug fixed as soon as possible, there would also be the possibility to create a DSA guest account to gain access to stadler.debian.net which is a SPARC T4 running Debian unstable. See: https://dsa.debian.org/doc/guest-account/ Since you're a DD, you can request a DSA guest account for them. They will need to specify what architectures they need access to. Access to other architectures is available as well, also through the GCC Compile Farm. I highly recommend the MariaDB people to request a GCC Compile Farm account if they haven't done so yet. I assume they would be interested to test their software on the various architectures offered there as well. And maybe they can also just use the Solaris 11.4 SPARC M8 to fix the sparc64 crashes. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
