Source: virglrenderer
Version: 0.10.3-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=virglrenderer&arch=armel&ver=0.10.3-1&stamp=1664582880&raw=0
...
FAILED: src/libvirgl.a.p/venus_vkr_context.c.o
cc -Isrc/libvirgl.a.p -Isrc -I../src -I../src/gallium/include
-I../src/gallium/auxiliary -I../src/gallium/auxiliary/util -I. -I..
-I../src/venus -I../src/drm -I../src/drm/drm-uapi -Isrc/mesa -I../src/mesa
-I../src/mesa/compat -I../src/mesa/pipe -I../src/mesa/util
-I/usr/include/libdrm -fdiagnostics-color=always -DNDEBUG
-D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Wpedantic -std=gnu11 -O0
-Werror=implicit-function-declaration -Werror=missing-prototypes
-Wmissing-prototypes -Werror=incompatible-pointer-types
-Werror=int-to-pointer-cast -Wno-overlength-strings -fvisibility=hidden
-imacros /<<PKGBUILDDIR>>/obj-arm-linux-gnueabi/config.h -DHAVE_CONFIG_H=1 -g
-O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ
src/libvirgl.a.p/venus_vkr_context.c.o -MF
src/libvirgl.a.p/venus_vkr_context.c.o.d -o
src/libvirgl.a.p/venus_vkr_context.c.o -c ../src/venus/vkr_context.c
In file included from ../src/mesa/util/compiler.h:37,
from ../src/mesa/util/xxhash.h:81,
from ../src/venus/vkr_context.c:17:
../src/venus/vkr_ring.h:33:1: error: static assertion failed: "vkr_ring_control
requires lock-free 32-bit atomic_uint"
33 | static_assert(ATOMIC_INT_LOCK_FREE == 2 && sizeof(atomic_uint) == 4,
| ^~~~~~~~~~~~~
...
Do src/venus/vkr_ring.h and src/proxy/proxy_context.h
really require ATOMIC_INT_LOCK_FREE == 2?
Atomics on armel being implemented with a kernel helper,
which gives only ATOMIC_INT_LOCK_FREE == 1.
If ATOMIC_INT_LOCK_FREE == 2 is really required, then disabling
venus and renderserver on armel should workaround it for now.
