Source: redland Version: 1.0.17-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20161118 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=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > -I/usr/include/mysql > -fdebug-prefix-map=/build/mysql-5.7-lG4h93/mysql-5.7-5.7.16=. .specs > -fabi-version=2 -fno-omit-frame-pointer -Wdate-time -D_FORTIFY_SOURCE=2 > -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/raptor2 -I/usr/include/rasqal > -I/usr/include/raptor2 > -DREDLAND_MODULE_PATH="\""/usr/local/lib/redland:/usr/lib/x86_64-linux-gnu/redland"\"" > -DLIBRDF_INTERNAL=1 -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. > -fstack-protector-strong -Wformat -Werror=format-security -c -o > librdf_storage_mysql_la-rdf_storage_mysql.lo `test -f 'rdf_storage_mysql.c' > || echo './'`rdf_storage_mysql.c > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I/usr/include/mysql > -fdebug-prefix-map=/build/mysql-5.7-lG4h93/mysql-5.7-5.7.16=. .specs > -fabi-version=2 -fno-omit-frame-pointer -Wdate-time -D_FORTIFY_SOURCE=2 > -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/raptor2 -I/usr/include/rasqal > -I/usr/include/raptor2 > -DREDLAND_MODULE_PATH=\"/usr/local/lib/redland:/usr/lib/x86_64-linux-gnu/redland\" > -DLIBRDF_INTERNAL=1 -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. > -fstack-protector-strong -Wformat -Werror=format-security -c > rdf_storage_mysql.c -fPIC -DPIC -o > .libs/librdf_storage_mysql_la-rdf_storage_mysql.o > gcc: error: .specs: No such file or directory > Makefile:1150: recipe for target > 'librdf_storage_mysql_la-rdf_storage_mysql.lo' failed > make[4]: *** [librdf_storage_mysql_la-rdf_storage_mysql.lo] Error 1 The full build log is available from: http://aws-logs.debian.net/2016/11/18/redland_1.0.17-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.
