Bug#1118365: chafa: FTBFS on i386

[Jochen Sprickerhof]

Hi Hans Petter,

* Hans Petter Jansson <h...@hpjansson.org> [2025-12-26 21:14]:

I tried to address this in the 1.18.0 upstream release, and also added
some extra output to the failing test. Unfortunately, it's not enough
to pinpoint the problem. I also haven't been able to trigger it on qemu
or any of the hardware I have access to.

Is there a way I can set up a test repository to throw a couple of
ideas at the wall and try to build it on the failing platform without
affecting any of the official repos?

git clone https://salsa.debian.org/debian/chafa.git
cd chafa
sed -i 's/g_atomic_int_get.*/24;/' chafa/chafa-features.c
sbuild -d sid --arch=i386 --no-source \
  --dpkg-source-opts="-Zgzip -z1 --format=1.0 -sn" \
  --chroot-mode=unshare --no-clean-source

Cheers Jochen

This seems to depend on the number of CPUs in the system and I can reproduce it on Debian stable with:

signature.asc
Description: PGP signature