public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "brechtsanders at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/105506] Error building GCC 12.1.0 against MinGW-w64: fatal error: cannot execute 'cc1': CreateProcess: No such file or directory
Date: Fri, 27 May 2022 09:48:36 +0000	[thread overview]
Message-ID: <bug-105506-4-z6TX0KzUCb@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

--- Comment #2 from Brecht Sanders <brechtsanders at users dot sourceforge.net> ---
I did an additional test to see where gcc.exe is looking for cc1.exe using
Process Monitor.

This was using a i686 UCRT build of GCC against MinGW-w64 installed under:
D:\Prog\winlibs32ucrt_stage\mingw32

I'm on Windows 11.

First it looks here (opening the file handle with CreateFile):
D:\Prog\winlibs32ucrt_stage\mingw32\libexec\gcc\i686-w64-mingw32ucrt\12.1.0\cc1.exe
This actually exists.

But then a call to QueryInformationVolume fails with BUFFER OVERFLOW
and then agian another call to QueryAllInformationFile also fails with BUFFER
OVERFLOW

Then it goes on to look for cc1.exe in places where it doesn't exist.

  parent reply	other threads:[~2022-05-27  9:48 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 [this message]
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 ` [Bug target/105506] [12/13 Regression] " rguenth at gcc dot gnu.org
2023-01-16 19:18 ` 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-z6TX0KzUCb@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: link
Be 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).