When emerging groff, it hits a point where it just spews out 20 of these per second: post-grohtml:<standard input>:61232: missing argument ... post-grohtml:<standard input>:61232: misCaught signal 2 make[2]: *** Deleting file `pic.html' make[2]: *** wait: No child processes. Stop. make[2]: *** Waiting for unfinished jobs.... make[2]: *** wait: No child processes. Stop. make[1]: *** [doc] Error 2 make: *** [all] Interrupt According to top, the spinning culprit is troff. Given how hackish all the current groff ebuilds are, my first guess would be that someone's hacked something unsafe. Reproducible: Always Steps to Reproduce: emerge >=sys-apps/groff-1.18.1-r2 Actual Results: Ebuild falls into an infinite loop and the machine starts being a very effective space heater. Expected Results: Emerge correctly, or at least bail out gracefully. I've gone so far as to check the drive for bad blocks & run memtest. Nothing wrong there. r2 and r3 also exhibit this behaviour. Only r1 emerges correctly. I don't know what all the patching and sed'ing is for, but it seems like an awful lot of it for something that should configure & install from vanilla sources.
what about groff-1.19.1 ?
groff-1.18.1-r4 and groff-1.19.1 emerge correctly, so it seems this bug is fixed.
ok, please reopen if the bug hits you again
