Source: libkqueue
Version: 2.0.3-1.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.   
> -Wdate-time -D_FORTIFY_SOURCE=2 -I./src/common -I./include -Wall -Wextra 
> -Wno-missing-field-initializers -Werror -g -O2 -std=c99 -D_XOPEN_SOURCE=600 
> -fvisibility=hidden -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o src/linux/libkqueue_la-read.lo `test -f 
> 'src/linux/read.c' || echo './'`src/linux/read.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 
> -I./src/common -I./include -Wall -Wextra -Wno-missing-field-initializers 
> -Werror -g -O2 -std=c99 -D_XOPEN_SOURCE=600 -fvisibility=hidden -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -c src/linux/read.c 
>  -fPIC -DPIC -o src/linux/.libs/libkqueue_la-read.o
> src/linux/read.c: In function 'evfilt_read_knote_delete':
> src/linux/read.c:207:74: error: comparison of constant '0' with boolean 
> expression is always false [-Werror=bool-compare]
>      if ((kn->kn_flags & KNFL_REGULAR_FILE && kn->kdata.kn_eventfd != -1) < 
> 0) {
>                                                                           ^
> cc1: all warnings being treated as errors
> make[2]: *** [src/linux/libkqueue_la-read.lo] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/13/libkqueue_2.0.3-1.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.

Reply via email to