Source: multipath-tools
Version: 0.7.9-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):
> make[2]: Entering directory '/<<PKGBUILDDIR>>/libmultipath'
> /bin/sh: 1: Syntax error: "(" unexpected
> Checking for dm_task_no_flush in /usr/include/libdevmapper.h ... yes
> Checking for dm_task_set_cookie in /usr/include/libdevmapper.h ... yes
> Checking for udev_monitor_set_receive_buffer_size in /usr/include/libudev.h 
> ... yes
> Checking for dm_task_deferred_remove in /usr/include/libdevmapper.h ... yes
> building memory.o because of memory.c
> cc -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>/libmultipath=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -O2 -g -pipe -Wall -Wextra -Wformat=2 
> -Werror=implicit-int -Werror=implicit-function-declaration 
> -Werror=format-security -Wno-sign-compare -Wno-unused-parameter 
> -Wno-clobbered -Werror=cast-qual -Werror=discarded-qualifiers 
> -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector-strong --param=ssp-buffer-size=4 
> -DBIN_DIR=\"/sbin\" -DLIB_STRING=\"/lib\" -DRUN_DIR=\"run\" -MMD -MP -g -O2 
> -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -fPIC -I../libmpathcmd -I../libmpathpersist 
> -DUSE_SYSTEMD=241 (241) -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE 
> -DLIBUDEV_API_RECVBUF -DLIBDM_API_DEFERRED -c -o memory.o memory.c
> /bin/sh: 1: Syntax error: "(" unexpected
> make[2]: *** [../Makefile.inc:137: memory.o] Error 2

The full build log is available from:
   http://aws-logs.debian.net/2019/03/15/multipath-tools_0.7.9-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