Your message dated Fri, 2 Oct 2020 18:26:23 +0200
with message-id <20201002162623.ga93...@i5.cruise.homelinux.net>
and subject line (RESEND) Fixed upstream
has caused the Debian Bug report #966850,
regarding iverilog: FTBFS: parse.cc:299:10: fatal error: parse.hh: No such file
or directory
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
966850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966850
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: iverilog
Version: 10.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):
> g++ -I. -I.. -I../libmisc -Wdate-time -D_FORTIFY_SOURCE=2 -DHAVE_CONFIG_H
> -Wall -Wextra -Wshadow -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=.
> -fstack-protector-strong -Wformat -Werror=format-security -MD -c parse.cc -o
> parse.o
> parse.cc:299:10: fatal error: parse.hh: No such file or directory
> 299 | #include "parse.hh"
> | ^~~~~~~~~~
> compilation terminated.
> make[2]: *** [Makefile:108: parse.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/08/02/iverilog_10.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.
--- End Message ---
--- Begin Message ---
Version: 11.0-1
Closing this report as the issue is fixed by the latest upstream, I
forgot to add this bug report to the changelog for 11.0-1.
Regards
Carsten
--- End Message ---
