This FTBFS is caused by a change in behaviour in bison 3.7. There's a
proposed fix upstream at

  https://github.com/verilator/verilator/pull/2505

which works by telling Bison the correct header name.


Rupert

Reply via email to