Source: thin-provisioning-tools
Version: 0.7.6-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20190315 qa-ftbfs
Justification: FTBFS in buster on amd64

Hi,

During a rebuild of all packages in buster (in a buster chroot, not a
sid chroot), your package failed to build on amd64.

Relevant part (hopefully):
> g++ -MM -MT thin-provisioning/shared_library_emitter.o -I. -I. 
> -I./thin-provisioning -I. -Igoogletest/googlemock/include 
> -Igoogletest/googletest/include -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -g -Wall -fPIC 
> -fno-strict-aliasing -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2  -DSTRERROR_R_CHAR_P  
> thin-provisioning/shared_library_emitter.cc > 
> thin-provisioning/shared_library_emitter.$$; \
> sed 's,\([^ :]*\)\.o[ :]*,\1.o \1.gmo 
> thin-provisioning/shared_library_emitter : Makefile ,g' < 
> thin-provisioning/shared_library_emitter.$$ > 
> thin-provisioning/shared_library_emitter.d; \
> rm -f thin-provisioning/shared_library_emitter.$$
> ft-lib/bcache.c:35:13: error: conflicting types for 'raise'
>  static void raise(const char *fmt, ...)
>              ^~~~~
> In file included from /usr/include/libaio.h:32,
>                  from ft-lib/bcache.c:12:
> /usr/include/signal.h:123:12: note: previous declaration of 'raise' was here
>  extern int raise (int __sig) __THROW;
>             ^~~~~
> make[1]: *** [<builtin>: ft-lib/bcache.o] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/2019/03/15/thin-provisioning-tools_0.7.6-2_testing.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