Source: valgrind Version: 1:3.7.0-5 Severity: serious Tags: wheezy sid User: [email protected] Usertags: qa-ftbfs-20120604 qa-ftbfs Justification: FTBFS on amd64
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -I../VEX/pub > -DVGA_x86=1 -DVGO_linux=1 -DVGP_x86_linux=1 -DVGPV_x86_linux_vanilla=1 > -I../coregrind -DVG_LIBDIR="\"/usr/lib/valgrind"\" > -DVG_PLATFORM="\"x86-linux\"" -m32 -O2 -g -Wall -Wmissing-prototypes > -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations > -Wno-format-zero-length -fno-strict-aliasing -fno-builtin -Wno-long-long -g > -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat > -Werror=format-security -D_FORTIFY_SOURCE=2 -Wno-pointer-sign > -fno-stack-protector -c -o libcoregrind_x86_linux_a-readstabs.o `test -f > 'm_debuginfo/readstabs.c' || echo './'`m_debuginfo/readstabs.c > m_debuginfo/readstabs.c:55:39: fatal error: a.out.h: No such file or directory > compilation terminated. > make[5]: *** [libcoregrind_x86_linux_a-readstabs.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/04/valgrind_3.7.0-5_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]
