Bug#952009: c-icap-modules: FTBFS: clamav_mod.c:108:13: error: expected identifier or ‘(’ before string constant
Source: c-icap-modules
Version: 1:0.5.3-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /bin/bash ../../libtool --tag=CC --mode=link gcc -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -fvisibility=hidden -DCI_BUILD_MODULE -D_REENTRANT -g -O2 -fdebug-prefix-map=/build/c-icap-FHVm1G/c-icap-0.5.3=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wall -D_FILE_OFFSET_BITS=64 -I/usr/include -I/usr/include/c_icap -module -avoid-version -Wl,-z,relro -Wl,-z,now -o clamd_mod.la -rpath /usr/lib/x86_64-linux-gnu/c_icap/ clamd_mod_la-clamd_mod.lo
> libtool: link: gcc -shared -fPIC -DPIC .libs/clamd_mod_la-clamd_mod.o -g -O2 -fstack-protector-strong -g -O2 -fstack-protector-strong -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,-soname -Wl,clamd_mod.so -o .libs/clamd_mod.so
> In file included from /usr/include/clamav.h:69,
> from clamav_mod.c:27:
> clamav_mod.c:108:13: error: expected identifier or ‘(’ before string constant
> 108 | static char CLAMAV_VERSION[CLAMAV_VERSION_SIZE];
> | ^~~~~~~~~~~~~~
> clamav_mod.c: In function ‘clamav_set_versions’:
> clamav_mod.c:645:6: warning: assignment of read-only location ‘"0.102.2"[63]’
> 645 | CLAMAV_VERSION[CLAMAV_VERSION_SIZE - 1] = '\0';
> | ^~~~~~~~~~~~~~
> make[4]: *** [Makefile:512: clamav_mod_la-clamav_mod.lo] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/02/22/c-icap-modules_0.5.3-2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
Reply to: