[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1065793: marked as done (charliecloud: FTBFS on arm{el,hf}: ch_fuse.c:68:19: error: initialization of ‘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)’} [-Werror=incompatible-pointer-types])

Your message dated Sat, 16 Mar 2024 21:44:30 +0000
with message-id <330c40b3-84f9-412b-b256-55d5841c3afe@posteo.de>
and subject line Re: Bug#1065793: charliecloud: FTBFS on arm{el,hf}: ch_fuse.c:68:19: error: initialization of ‘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)’} [-Werror=incompatible-pointer-types]
has caused the Debian Bug report #1065793,
regarding charliecloud: FTBFS on arm{el,hf}: ch_fuse.c:68:19: error: initialization of ‘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)’} [-Werror=incompatible-pointer-types]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1065793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065793
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: charliecloud
Version: 0.37-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramacher@debian.org

https://buildd.debian.org/status/fetch.php?pkg=charliecloud&arch=armhf&ver=0.37-1&stamp=1709893440&raw=0

gcc -DHAVE_CONFIG_H -I.   -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -std=c99 -Wall -Werror -I/usr/include/fuse3  -pthread -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -std=c99 -Wall -Werror -I/usr/include/fuse3  -c -o ch_run-ch_fuse.o `test -f 'ch_fuse.c' || echo './'`ch_fuse.c
rm -f ch-run-oci
rm -f ch-image
sed -E 's|%PYTHON_SHEBANG%|/usr/bin/env python3|' < ch-run-oci.py.in > ch-run-oci
sed -E 's|%PYTHON_SHEBANG%|/usr/bin/env python3|' < ch-image.py.in > ch-image
chmod +rx,-w ch-run-oci  # respects umask
chmod +rx,-w ch-image  # respects umask
ch_fuse.c:68:19: error: initialization of ‘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)’} [-Werror=incompatible-pointer-types]
   68 |     .forget     = &sqfs_ll_op_forget,
      |                   ^
ch_fuse.c:68:19: note: (near initialization for ‘OPS.forget’)
cc1: all warnings being treated as errors
make[3]: *** [Makefile:625: ch_run-ch_fuse.o] Error 1

Cheers
-- 
Sebastian Ramacher

--- End Message ---
--- Begin Message --- 
Source: charliecloud
Source-Version: 0.37-2
Done: Peter Wienemann <fossdev@posteo.de>

On 2024-03-16 14:30:49 +0100, Peter Wienemann wrote:

It seems that the patch uploaded with 0.37-2 does not fix this issue.
It turns out (see comment in the upstream PR [0]) that in addition to the patch applied to charliecloud, a full fix also requires patching/updating squashfuse. As a result I have filed a new bug [1] (affecting src:charliecloud) and close this one. 

Best regards,

Peter

[0] https://github.com/hpc/charliecloud/pull/1859#issuecomment-2002039569
[1] https://bugs.debian.org/1067010

--- End Message ---
Reply to: