https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113749
--- Comment #3 from Samuel Thibault <samuel.thiba...@ens-lyon.org> --- I don't think it is a regression. We noticed it only recently in Debian only because the configuration files got bogus. See for instance https://buildd.debian.org/status/fetch.php?pkg=gcc-13&arch=hurd-i386&ver=13.2.0-10&stamp=1705711375&raw= which fails the same: m2/boot-bin/mc --olang=c++ --h-file-prefix=G -I../../src/gcc/m2/gm2-libs -I../../src/gcc/m2/gm2-compiler -I../../src/gcc/m2/gm2-libiberty -I E: Build killed with signal TERM after 180 minutes of inactivity And we can trace it back to this commit in debian: commit ac0e3d134553e01c04b6a1b7f9c855fcb747dd6f Author: Matthias Klose <d...@ubuntu.com> Date: Tue Oct 8 10:34:25 2019 +0200 * Disable gm2 on hurd-i386, mc hangs there (Samuel Thibault). Closes: #940600. That being said, it'd still be good to fix it, sure :)
