Bug#1060849: mesa: FTBFS on armel: static assertion failed: "vn_ring_shared requires lock-free 32-bit atomic_uint"
On Tue, Jan 16, 2024 at 11:02:25 +0100, Julien Cristau wrote: > On Mon, Jan 15, 2024 at 16:14:17 +, Simon McVittie wrote: > > > The armel baseline does not have lock-free atomic operation opcodes. The > > result is a build failure: > > > > https://buildd.debian.org/status/fetch.php?pkg=mesa=armel=23.3.3-1=1705055313=0 > > > In file included from ../src/util/u_math.h:43, > > > from ../src/virtio/vulkan/vn_common.h:35, > > > from ../src/virtio/vulkan/vn_buffer.h:14, > > > from ../src/virtio/vulkan/vn_buffer.c:11: > > > ../src/virtio/vulkan/vn_ring.h:40:1: error: static assertion failed: > > > "vn_ring_shared requires lock-free 32-bit atomic_uint" > > >40 | static_assert(ATOMIC_INT_LOCK_FREE == 2 && sizeof(atomic_uint) == > > > 4, > > > > Could this perhaps be solved by disabling the virtio driver on armel? > > > Looks like that already happened in > https://salsa.debian.org/xorg-team/lib/mesa/-/commit/71deba800f28059724dd7899b8901e86c0eb2365 > a few months ago, looks like it regressed. > Right, https://salsa.debian.org/xorg-team/lib/mesa/-/commit/9e99f52bf2c9c8f2993cc2a6bec1e13b70fd10b8 seems to have dropped the armel special-case there. Cheers, Julien
Bug#1060849: mesa: FTBFS on armel: static assertion failed: "vn_ring_shared requires lock-free 32-bit atomic_uint"
On Mon, Jan 15, 2024 at 16:14:17 +, Simon McVittie wrote: > The armel baseline does not have lock-free atomic operation opcodes. The > result is a build failure: > > https://buildd.debian.org/status/fetch.php?pkg=mesa=armel=23.3.3-1=1705055313=0 > > In file included from ../src/util/u_math.h:43, > > from ../src/virtio/vulkan/vn_common.h:35, > > from ../src/virtio/vulkan/vn_buffer.h:14, > > from ../src/virtio/vulkan/vn_buffer.c:11: > > ../src/virtio/vulkan/vn_ring.h:40:1: error: static assertion failed: > > "vn_ring_shared requires lock-free 32-bit atomic_uint" > >40 | static_assert(ATOMIC_INT_LOCK_FREE == 2 && sizeof(atomic_uint) == 4, > > Could this perhaps be solved by disabling the virtio driver on armel? > Looks like that already happened in https://salsa.debian.org/xorg-team/lib/mesa/-/commit/71deba800f28059724dd7899b8901e86c0eb2365 a few months ago, looks like it regressed. Cheers, Julien
Bug#1060849: mesa: FTBFS on armel: static assertion failed: "vn_ring_shared requires lock-free 32-bit atomic_uint"
Source: mesa Version: 23.3.3-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: debian-...@lists.debian.org User: debian-...@lists.debian.org Usertags: armel Control: block 1060779 by -1 The armel baseline does not have lock-free atomic operation opcodes. The result is a build failure: https://buildd.debian.org/status/fetch.php?pkg=mesa=armel=23.3.3-1=1705055313=0 > In file included from ../src/util/u_math.h:43, > from ../src/virtio/vulkan/vn_common.h:35, > from ../src/virtio/vulkan/vn_buffer.h:14, > from ../src/virtio/vulkan/vn_buffer.c:11: > ../src/virtio/vulkan/vn_ring.h:40:1: error: static assertion failed: > "vn_ring_shared requires lock-free 32-bit atomic_uint" >40 | static_assert(ATOMIC_INT_LOCK_FREE == 2 && sizeof(atomic_uint) == 4, Could this perhaps be solved by disabling the virtio driver on armel? Thanks, smcv
