public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "samuel.thibault@ens-lyon.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug modula2/113749] [14 Regression] m2 enabled build times out on i686-gnu (GNU Hurd) Date: Thu, 22 Feb 2024 23:15:56 +0000 [thread overview] Message-ID: <bug-113749-4-EriZKQcQtm@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113749-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113749 --- Comment #3 from Samuel Thibault <samuel.thibault@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 <doko@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 :)
next prev parent reply other threads:[~2024-02-22 23:15 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-03 18:43 [Bug modula2/113749] New: " doko at gcc dot gnu.org 2024-02-05 9:02 ` [Bug modula2/113749] " rguenth at gcc dot gnu.org 2024-02-06 11:10 ` gaius at gcc dot gnu.org 2024-02-22 21:19 ` gaius at gcc dot gnu.org 2024-02-22 23:15 ` samuel.thibault@ens-lyon.org [this message] 2024-02-24 1:55 ` gaius at gcc dot gnu.org 2024-02-24 3:14 ` gaius at gcc dot gnu.org 2024-02-25 11:09 ` cvs-commit at gcc dot gnu.org 2024-02-25 11:13 ` gaius at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-113749-4-EriZKQcQtm@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).