public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/105506] [12/13 Regression] Error building GCC 12.1.0 against MinGW-w64: fatal error: cannot execute 'cc1': CreateProcess: No such file or directory Date: Mon, 16 Jan 2023 10:44:03 +0000 [thread overview] Message-ID: <bug-105506-4-mT3dsyDpg7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105506-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105506 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |12.3 Priority|P3 |P2
next prev parent reply other threads:[~2023-01-16 10:44 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-06 15:06 [Bug c/105506] New: " brechtsanders at users dot sourceforge.net 2022-05-14 18:42 ` [Bug target/105506] " brechtsanders at users dot sourceforge.net 2022-05-27 9:48 ` brechtsanders at users dot sourceforge.net 2022-05-27 11:34 ` brechtsanders at users dot sourceforge.net 2022-06-05 14:28 ` brechtsanders at users dot sourceforge.net 2022-06-05 14:34 ` brechtsanders at users dot sourceforge.net 2022-06-05 20:19 ` martin at martin dot st 2022-06-06 9:00 ` brechtsanders at users dot sourceforge.net 2022-06-06 11:07 ` martin at martin dot st 2023-01-16 10:44 ` rguenth at gcc dot gnu.org [this message] 2023-01-16 19:18 ` [Bug target/105506] [12/13 Regression] " hjl.tools at gmail dot com 2023-01-16 21:32 ` brechtsanders at users dot sourceforge.net 2023-01-16 22:31 ` hjl.tools at gmail dot com 2023-01-18 20:19 ` brechtsanders at users dot sourceforge.net 2023-02-01 21:52 ` hjl.tools at gmail dot com 2023-05-08 12:24 ` [Bug target/105506] [12/13/14 " rguenth 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-105506-4-mT3dsyDpg7@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).