Bug#831132: xlog: FTBFS with GCC 6: adif2.c:59:19: error: 'adif_widths' defined but not used [-Werror=unused-const-variable=]
Source: xlog
Version: 2.0.13-2
Severity: serious
Tags: stretch sid
User: debian-qa@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64
Hi,
During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg00007.html
Relevant part (hopefully):
> x86_64-linux-gnu-gcc -DPACKAGE_NAME=\"xlog\" -DPACKAGE_TARNAME=\"xlog\" -DPACKAGE_VERSION=\"2.0.13\" -DPACKAGE_STRING=\"xlog\ 2.0.13\" -DPACKAGE_BUGREPORT=\"andystewart@comcast.net\" -DPACKAGE_URL=\"\" -DPACKAGE=\"xlog\" -DVERSION=\"2.0.13\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_IPC_H=1 -DHAVE_SYS_SHM_H=1 -DHAVE_STRPTIME=1 -DHAVE_STRCHR=1 -DHAVE_INDEX=1 -DENABLE_NLS=1 -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 -I. -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -g -O2 -Wall -Wno-unused-but-set-variable -Werror -MT adif2.o -MD -MP -MF .deps/adif2.Tpo -c -o adif2.o adif2.c
> adif2.c:59:19: error: 'adif_widths' defined but not used [-Werror=unused-const-variable=]
> static const gint adif_widths[] = { 15, 8, 15, 15, 8, 8, 8, 8, 8, 80, 8, 8, 8,
> ^~~~~~~~~~~
> cc1: all warnings being treated as errors
> make[3]: *** [adif2.o] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2016/07/13/xlog_2.0.13-2_unstable_gcc6.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: