Source: rhmessaging
Version: 0.16-1
Severity: serious
Tags: jessie sid
User: [email protected]
Usertags: qa-ftbfs-20130726 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):
> /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I..
> -D_FORTIFY_SOURCE=2 -Werror -pedantic -Wall -Wextra -Wno-shadow
> -Wpointer-arith -Wcast-qual -Wcast-align -Wno-long-long
> -Wvolatile-register-var -Winvalid-pch -Wno-system-headers -I/usr/include
> -I./gen -DRHM_CLEAN -pthread -g -O2 -fstack-protector
> --param=ssp-buffer-size=4 -Wformat -Werror=format-security
> -Wno-error=cast-qual -Wno-error=cast-align -c -o rmgr.lo `test -f
> 'jrnl/rmgr.cpp' || echo './'`jrnl/rmgr.cpp
> libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -Werror
> -pedantic -Wall -Wextra -Wno-shadow -Wpointer-arith -Wcast-qual -Wcast-align
> -Wno-long-long -Wvolatile-register-var -Winvalid-pch -Wno-system-headers
> -I/usr/include -I./gen -DRHM_CLEAN -pthread -g -O2 -fstack-protector
> --param=ssp-buffer-size=4 -Wformat -Werror=format-security
> -Wno-error=cast-qual -Wno-error=cast-align -c jrnl/rmgr.cpp -fPIC -DPIC -o
> .libs/rmgr.o
> jrnl/rmgr.cpp: In member function 'void
> mrg::journal::rmgr::initialize(mrg::journal::aio_callback*)':
> jrnl/rmgr.cpp:75:44: error: argument to 'sizeof' in 'void* memset(void*, int,
> size_t)' call is the same pointer type 'mrg::journal::aio_cb* {aka iocb*}' as
> the destination; expected 'mrg::journal::aio_cb {aka iocb}' or an explicit
> length [-Werror=sizeof-pointer-memaccess]
> std::memset(_fhdr_aio_cb_ptr, 0, sizeof(aio_cb*));
> ^
> cc1plus: all warnings being treated as errors
> make[4]: *** [rmgr.lo] Error 1
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2013/07/26/rhmessaging_0.16-1_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.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
