Hi,

> Thank you for the feedback, the commit that broke yosys was
> b32f8bc9da74158330cebdbcb481d41e1be6d1ce when iverilog was updated to
> 12.0
Thanks a lot for the information. I also have yosys that fails because
of the missing zlib but it wasn't clear why it became needed out of the
blue. I've not build-tested the patch yet though.

The commit b32f8bc9da74158330cebdbcb481d41e1be6d1ce ("gnu: iverilog:
Update to 12.0."), also brings more questions. In it we have:
-    (native-inputs
-     (list flex bison ghostscript zlib))   ; ps2pdf
+    (native-inputs (list autoconf bison flex gperf))

So do we also need Ghostscript ? Though if it builds and run fine
without Ghostscript maybe ghostscript got removed because it wasn't
useful?

Also would it help if I package some functional test(s) for the FPGA
toolchain? Personally I found that it made it easier to test the
packages when I maintained them for Parabola.

Though the "functional test" I have is just the FOMU workshop code that
I modified to blink blue instead of other colors:
https://git.parabola.nu/fpga/fomu-verilog-blue-blink.git/

The downside is that tests like that are specific to an FPGA model so
I'm unsure if this is a good idea or not.

Also note that I don't know FPGAs well. I just got one to maintain some
Parabola packages.

Denis.