Trying to emerge iverilog with the stable x86 flag set, portage attempts to merge with version 0.7. The URI in the ebuild refers to a broken snapshot of 0.7. This is obviously not a portage problem, but it is interesting that a broken snapshot is used for the 'stable' build, while the unstable flag ~x86 works. I have verified that 0.7 tarball is broken by downloading the file by hand and attempting to install. Reproducible: Always Steps to Reproduce: 1. emerge iverilog (with USE="x86") 2. compile dies during compilation of load_module.cc 3. Actual Results: Build stops due to compilation failure. The tar.gz contains broken code. Expected Results: Build works, iverilog is installed correctly. I understand that we have no control over bad files upstream, but should broken code be chosen for the stable build over working code (i.e. verilog-0.8)?
0.8 is only in portage for a few days, but considering that I can't get 0.7 to build with gcc 3.3 or 3.4 I think you are right. Looks like most people who use it emerged it long ago in the past when it still went through the compiler.
0.8 stabled on x86 in CVS; please reopen this bug and let me know if that also has issues. Thanks!
