Source: gecode Version: 5.1.0-2 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20171030 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. -fcx-limited-range -fno-signaling-nans -fno-rounding-math > -ffinite-math-only -fno-math-errno -fno-strict-aliasing -fvisibility=hidden > -ggdb -std=c++11 -pipe -Wall -Wextra -fPIC -pthread -DNDEBUG -g -O2 > -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat > -Werror=format-security -O3 -D_REENTRANT -Wdate-time -D_FORTIFY_SOURCE=2 \ > \ > -c -o gecode/gist/drawingcursor.o gecode/gist/drawingcursor.cpp > In file included from ./gecode/gist/spacenode.hh:41:0, > from ./gecode/gist/visualnode.hh:41, > from ./gecode/gist/nodecursor.hh:41, > from ./gecode/gist/drawingcursor.hh:41, > from gecode/gist/drawingcursor.cpp:38: > ./gecode/gist/node.hh:43:10: fatal error: QHash: No such file or directory > #include <QHash> > ^~~~~~~ > compilation terminated. > Makefile:1415: recipe for target 'gecode/gist/drawingcursor.o' failed > make[2]: *** [gecode/gist/drawingcursor.o] Error 1 The full build log is available from: http://aws-logs.debian.net/2017/10/30/gecode_5.1.0-2_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.