Source: urweb Version: 20160515+dfsg-1 Severity: serious Tags: stretch sid User: debian...@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): > /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > -I../../include/urweb -I./../../include/urweb -I/usr/include -Wdate-time > -D_FORTIFY_SOURCE=2 -Wimplicit -Wall -Werror -Wno-deprecated-declarations > -pthread -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c > -o memmem.lo memmem.c > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../include/urweb > -I./../../include/urweb -I/usr/include -Wdate-time -D_FORTIFY_SOURCE=2 > -Wimplicit -Wall -Werror -Wno-deprecated-declarations -pthread -g -O2 > -fstack-protector-strong -Wformat -Werror=format-security -c memmem.c -fPIC > -DPIC -o .libs/memmem.o > memmem.c: In function 'memmem': > memmem.c:77:17: error: this 'if' clause does not guard... > [-Werror=misleading-indentation] > if (*sp == *pp) > ^~ > memmem.c:81:25: note: ...this statement, but the latter is misleadingly > indented as if it is guarded by the 'if' > sp++; > ^~ > memmem.c:73:14: error: nonnull argument 'b1' compared to NULL > [-Werror=nonnull-compare] > if(!(b1 && b2 && len1 && len2)) > ^~ > memmem.c:73:17: error: nonnull argument 'b2' compared to NULL > [-Werror=nonnull-compare] > if(!(b1 && b2 && len1 && len2)) > ^~ > cc1: all warnings being treated as errors > make[2]: *** [memmem.lo] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2016/07/13/urweb_20160515+dfsg-1_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.
