Package: libsquashfuse-dev Version: 0.5.0-2 Severity: serious Tags: ftbfs fixed-upstream Affects: src:charliecloud
Dear Maintainer, squashfuse suffers from an incompatible pointer type issue on 32-bit architectures. Checking the latest build logs for armel, armhf and i386 ([0], [1], [2]) one finds the following warning: ll_main.c: In function ‘main’: ll_main.c:164:41: warning: assignment to ‘void (*)(struct fuse_req *, fuse_ino_t, uint64_t)’ {aka ‘void (*)(struct fuse_req *, long long unsigned int, long long unsigned int)’} from incompatible pointer type ‘void (*)(struct fuse_req *, fuse_ino_t, long unsigned int)’ {aka ‘void (*)(struct fuse_req *, long long unsigned int, long unsigned int)’} [-Wincompatible-pointer-types] 164 | sqfs_ll_ops.forget = sqfs_ll_op_forget; | ^ This incompatibility leads to an FTBFS issue for the charliecloud package on 32-bit architectures (see e. g. [3]) since it is built using the -Werror option. It seems that this issue was fixed in upstream release 0.5.1 [4]. More background information on this issue can be obtained from the corresponding Charliecloud upstream issue and PR ([5], [6]). Best regards, Peter [0] https://buildd.debian.org/status/fetch.php?pkg=squashfuse&arch=armel&ver=0.5.0-2%2Bb1&stamp=1707534165&raw=0 [1] https://buildd.debian.org/status/fetch.php?pkg=squashfuse&arch=armhf&ver=0.5.0-2%2Bb1&stamp=1707538322&raw=0 [2] https://buildd.debian.org/status/fetch.php?pkg=squashfuse&arch=i386&ver=0.5.0-2%2Bb1&stamp=1707537260&raw=0 [3] https://buildd.debian.org/status/fetch.php?pkg=charliecloud&arch=armel&ver=0.37-2&stamp=1710594551&file=log [4] https://github.com/vasi/squashfuse/commit/cb148fc1477ed676049b7891ebb6efc90b2c00ec [5] https://github.com/hpc/charliecloud/issues/1858 [6] https://github.com/hpc/charliecloud/pull/1859