Source: minizinc Version: 2.4.3-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/c++ -DHAS_GECODE -I/<<PKGBUILDDIR>>/include > -I/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/include -g -O2 > -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++11 -o > CMakeFiles/minizinc_parser.dir/regex_lexer.yy.cpp.o -c > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/regex_lexer.yy.cpp > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/parser.tab.cpp:178:10: fatal error: > parser.tab.hh: No such file or directory > 178 | #include "parser.tab.hh" > | ^~~~~~~~~~~~~~~ > compilation terminated. > make[3]: *** [CMakeFiles/minizinc_parser.dir/build.make:88: > CMakeFiles/minizinc_parser.dir/parser.tab.cpp.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/08/02/minizinc_2.4.3-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.
