Hi, On Thu, Sep 12, 2024 at 11:48:21AM +0100, Simon McVittie wrote:
Source: gtk4 Version: 4.14.4+ds-8 Severity: important Tags: ftbfs help X-Debbugs-Cc: debian-po...@lists.debian.orgweston might be broken on all -ports architectures and functional on all release architectures, but that level of coincidence seems a little far-fetched. So my next theory for this is that something is consistently different about the -ports buildds - perhaps their XDG_RUNTIME_DIR is set up differently? - and that is causing "debian/tests/run-with-display wayland" (or the copy of weston that it runs) to fail? After the failure mode discussed in this bug report has been addressed, it will become more useful to look at individual/isolated test failures (as separate bug reports, please). Based on the status of the less-production-ready release architectures like mips64el and riscv64, I suspect that the most common root cause for individual test failures will be the software OpenGL stack: implementation issues in Mesa's llvmpipe and softpipe, implementation issues in LLVM's old MCJIT and new ORCJIT, and the GTK packaging's choice of whether to mitigate llvmpipe bugs by forcing softpipe (currently done on mips*, riscv*, powerpc, sparc*) or test with llvmpipe (as we do on x86, ARM, etc.).
If I understand correctly, the gtk4 can be built[0] on riscv64 once llvm-18 got upload to riscv64[1]. I will look at the issue continuely.
Becasue #1080435 has been closed, so I can not reply to it directly. but I would like to suggest we can enable llvmpipe on riscv64. Mesa's llvmpipe even can be used before ORCJIT supported and orcjit issue on Debian should be fixed once llvm-18 uploaded again. Thanks for your time again. BR, Bo [0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080435#19 [1]: https://buildd.debian.org/status/package.php?p=llvm-toolchain-18
Thanks, smcv
signature.asc
Description: PGP signature
