Source: verilator Version: 4.036-1 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): > g++ -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong > -Wformat -Werror=format-security -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. > -fstack-protector-strong -Wformat -Werror=format-security -I/usr/include > -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 > -I/usr/include -MMD -I. -I.. -I.. -I../../include -I../../include -DYYDEBUG > -O2 -MP -faligned-new -Wno-unused-parameter -Wno-shadow > -DDEFENV_SYSTEMC=\"\" -DDEFENV_SYSTEMC_ARCH=\"\" > -DDEFENV_SYSTEMC_INCLUDE=\"\" -DDEFENV_SYSTEMC_LIBDIR=\"\" > -DDEFENV_VERILATOR_ROOT=\"/usr/share/verilator\" -Wno-char-subscripts > -Wno-unused -c ../V3ParseGrammar.cpp -o V3ParseGrammar.o > In file included from ../V3ParseGrammar.cpp:22: > verilog.c:313:10: fatal error: verilog.h: No such file or directory > compilation terminated. > make[3]: *** [../Makefile_obj:301: V3ParseGrammar.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/08/02/verilator_4.036-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.
