Source: dmtcp
Version: 2.3.1-6
Severity: serious
Tags: buster sid
User: [email protected]
Usertags: qa-ftbfs-20170719 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> g++ -I../../../jalib -I../../../include -I../../../include -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -DHAVE_CONFIG_H 
> -fPIC -g -c -o pid.o  pid.cpp
> In file included from pid.cpp:27:0:
> pidwrappers.h:191:20: error: '__WAIT_STATUS' was not declared in this scope
>    pid_t _real_wait(__WAIT_STATUS stat_loc);
>                     ^~~~~~~~~~~~~
> pidwrappers.h:195:21: error: '__WAIT_STATUS' was not declared in this scope
>    pid_t _real_wait3(__WAIT_STATUS status, int options, struct rusage 
> *rusage);
>                      ^~~~~~~~~~~~~
> pidwrappers.h:195:43: error: expected primary-expression before 'int'
>    pid_t _real_wait3(__WAIT_STATUS status, int options, struct rusage 
> *rusage);
>                                            ^~~
> pidwrappers.h:195:56: error: expected primary-expression before 'struct'
>    pid_t _real_wait3(__WAIT_STATUS status, int options, struct rusage 
> *rusage);
>                                                         ^~~~~~
> pidwrappers.h:195:77: error: expression list treated as compound expression 
> in initializer [-fpermissive]
>    pid_t _real_wait3(__WAIT_STATUS status, int options, struct rusage 
> *rusage);
>                                                                              ^
> pidwrappers.h:196:32: error: '__WAIT_STATUS' has not been declared
>    pid_t _real_wait4(pid_t pid, __WAIT_STATUS status, int options,
>                                 ^~~~~~~~~~~~~
> Makefile:117: recipe for target 'pid.o' failed
> make[4]: *** [pid.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2017/07/19/dmtcp_2.3.1-6_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 via email to