[Bug c/105506] New: Error building GCC 12.1.0 against MinGW-w64: fatal error: cannot execute 'cc1': CreateProcess: No such file or directory

[Bug c/105506] New: Error building GCC 12.1.0 against MinGW-w64: fatal error: cannot execute 'cc1': CreateProcess: No such file or directory

[brechtsanders at users dot sourceforge.net]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105506

            Bug ID: 105506
           Summary: Error building GCC 12.1.0 against MinGW-w64: fatal
                    error: cannot execute 'cc1': CreateProcess: No such
                    file or directory
           Product: gcc
           Version: 12.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: brechtsanders at users dot sourceforge.net
  Target Milestone: ---

Building GCC 12.1.0 against MinGW-w64 fails with (error taken from config.log
for libgcc folder):
fatal error: cannot execute 'cc1': CreateProcess: No such file or directory
in libgcc

I believe this fails because CreateProcess() probably expects this to be
cc1.exe

Where should this be fixed?

[Bug target/105506] Error building GCC 12.1.0 against MinGW-w64: fatal error: cannot execute 'cc1': CreateProcess: No such file or directory

[brechtsanders at users dot sourceforge.net]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105506

--- Comment #1 from Brecht Sanders <brechtsanders at users dot sourceforge.net> ---
Apparently this issue is not related to the .exe extension, but rather to where
it is looking for cc1.exe.

If somepath/bin is where gcc.exe lives than it helpst to add
somepath/libexec/gcc/x86_64-w64-mingw32/12.1.0 to the PATH to around this
issue.

But this should not be necessary.

I also find it strange that I don't have this issue with the MSVCRT build of
MinGW-w64, but I do have the issue with the UCRT build of MinGW-w64.

Is there a different path or architecture triplet at play for UCRT?

[Bug target/105506] Error building GCC 12.1.0 against MinGW-w64: fatal error: cannot execute 'cc1': CreateProcess: No such file or directory

[brechtsanders at users dot sourceforge.net]

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.

[Bug target/105506] Error building GCC 12.1.0 against MinGW-w64: fatal error: cannot execute 'cc1': CreateProcess: No such file or directory

[brechtsanders at users dot sourceforge.net]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105506

--- Comment #3 from Brecht Sanders <brechtsanders at users dot sourceforge.net> ---
Created attachment 53046
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53046&action=edit
ProcessMonitor filtered on occurrence of "cc1"

[Bug target/105506] Error building GCC 12.1.0 against MinGW-w64: fatal error: cannot execute 'cc1': CreateProcess: No such file or directory

[brechtsanders at users dot sourceforge.net]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105506

--- Comment #4 from Brecht Sanders <brechtsanders at users dot sourceforge.net> ---
I just ran `gcc -print-prog-name=cc1` and saw the output was only `cc1` while
on working versions it reports a full path to `cc1.exe` (e.g.
`d:/prog/winlibs64_stage/custombuilt/share/gcc/bin/../libexec/gcc/x86_64-w64-mingw32/12.1.0/cc1.exe`).

In this minimal case Process Monitor also shows the handle to `cc1.exe` is
successfully opened but the subsequent calls to QueryInformationVolume and
QueryAllInformationFile fail with BUFFER_OVERFLOW.

[Bug target/105506] Error building GCC 12.1.0 against MinGW-w64: fatal error: cannot execute 'cc1': CreateProcess: No such file or directory

[brechtsanders at users dot sourceforge.net]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105506

--- Comment #5 from Brecht Sanders <brechtsanders at users dot sourceforge.net> ---
Created attachment 53088
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53088&action=edit
Process Monitor when running `gcc -print-prog-name=cc1`

Process Monitor when running `gcc -print-prog-name=cc1`

[Bug target/105506] Error building GCC 12.1.0 against MinGW-w64: fatal error: cannot execute 'cc1': CreateProcess: No such file or directory

[martin at martin dot st]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105506

Martin Storsjö <martin at martin dot st> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |martin at martin dot st

--- Comment #6 from Martin Storsjö <martin at martin dot st> ---
This is an old longstanding issue that seems to have reappeared, but which has
been fixed differently recently in the very latest mingw-w64 git. But first a
brief history of the issue:

GCC uses the access() function for checking whether a binary exists and is
executable (with the X_OK flag as parameter). On Windows, there's no separate
"execute" permission bit, but the X_OK bit (which isn't a documented parameter
from Microsoft's side) used to be ignored.

In Vista, msvcrt.dll's access() function suddenly stopped ignoring the bit that
was used for X_OK (which mingw had decided to use for that purpose), and
started erroring out when this bit was set. This was dealt with in 2007 in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=33281, by adding a
reimplementation of the access() function in mingw. By defining
__USE_MINGW_ACCESS, the access() function is redirected to the __mingw_access()
function. GCC set -D__USE_MINGW_ACCESS when building on mingw to include this
workaround.

After some time, it seems like Microsoft reverted this behaviour in
msvcrt.dll's access() function, because now it no longer seems like this
behaviour is present, not on modern Windows 10, but not even on "modern"
installations of Vista either. So the need for -D__USE_MINGW_ACCESS has
vanished (and bitrotted in GCC somewhat).

UCRT's access() function does have the same issue though - if passed the
undocumented, mingw-invented X_OK bit, it errors out. As GCC did try to define
__USE_MINGW_ACCESS, the workaround should have been picked up though, but as
GCC's codebase had evolved, the define wasn't being set in all the cases where
it might have been needed. This was fixed for GCC 11 in
https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=89e95ad2e7679322b2f5ee9070ff2721d5ca1d6d
(and later backported to GCC 9 and 10 in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101238).

But apparently something has changed further in GCC 12, so that this define
doesn't end up set in all the places where it needs to. (It'd be interesting to
know why/where/when!) In mingw-w64, we decided to enable this workaround
unconditionally for UCRT (as a more general fix for other audiences, although
GCC is the only one I've heard of needing it) - skipping the UCRT provided
access() function and always using the mingw reimplementation, see
https://github.com/mingw-w64/mingw-w64/commit/bceadc54d8f32b3f14c69074892e2718eac08e3b.

So to successfully build GCC 12 running on UCRT, you'd need to use another GCC
install, with the very latest mingw-w64 (or an older release with that fix
cherry-picked, plus the following Makefile.in update from
https://github.com/mingw-w64/mingw-w64/commit/89bacd2be60fa92dd74d3b5f2074b06a32d8c784),
to build GCC 12. Alternatively, see if you can manually pass
-D__USE_MINGW_ACCESS to the GCC 12 build, if it'd end up in all the places
where it's needed.

[Bug target/105506] Error building GCC 12.1.0 against MinGW-w64: fatal error: cannot execute 'cc1': CreateProcess: No such file or directory

[brechtsanders at users dot sourceforge.net]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105506

--- Comment #7 from Brecht Sanders <brechtsanders at users dot sourceforge.net> ---
Thank you for sharing your insights.

I can confirm building with CFLAGS="-D__USE_MINGW_ACCESS" works.

So I guess the question that remains is: Where is -D__USE_MINGW_ACCES missing
in the configuration of GCC 12?

It would seem to me the answer lies in code added since GCC 11 that contains
access()/X_OK.

[Bug target/105506] Error building GCC 12.1.0 against MinGW-w64: fatal error: cannot execute 'cc1': CreateProcess: No such file or directory

[martin at martin dot st]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105506

--- Comment #8 from Martin Storsjö <martin at martin dot st> ---
(In reply to Brecht Sanders from comment #7)
> So I guess the question that remains is: Where is -D__USE_MINGW_ACCES
> missing in the configuration of GCC 12?
> 
> It would seem to me the answer lies in code added since GCC 11 that contains
> access()/X_OK.

I bisected, and it seems like a build system adjustment makes it lose the flags
that are added in config/mh-mingw (where they are added to CFLAGS, CXXFLAGS and
a bunch of other *_CXXFLAGS). The built GCC reproduces the issue since this
commit:

https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=4a5e71f2348adcc49939804889d9f1a64d97005a

Unfortunately, the build system changes here are slightly complex, so it's not
entirely obvious to me where the flags that are added to CFLAGS/CXXFLAGS are
lost.

(Due to other commits around it, cross compiling GCC from linux to windows
fails entirely, until a couple commits later though -
https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=ab18659afc054434cef4d4757a3519f1100adc52
- but I tested the commit above with this one cherrypicked on top.)

[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

[rguenth at gcc dot gnu.org]

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

[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

[hjl.tools at gmail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105506

--- Comment #9 from H.J. Lu <hjl.tools at gmail dot com> ---
Created attachment 54284
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54284&action=edit
A patch

Please try this.

[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

[brechtsanders at users dot sourceforge.net]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105506

--- Comment #10 from Brecht Sanders <brechtsanders at users dot sourceforge.net> ---
I can confirm GCC 12.2.0 builds fine with that patch and without CFLAG
-D__USE_MINGW_ACCESS

[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

[hjl.tools at gmail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105506

--- Comment #11 from H.J. Lu <hjl.tools at gmail dot com> ---
Created attachment 54288
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54288&action=edit
An updated patch

Try this one.

[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

[brechtsanders at users dot sourceforge.net]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105506

--- Comment #12 from Brecht Sanders <brechtsanders at users dot sourceforge.net> ---
I couldn't apply that patch. Is that for 12.2.0 ?

[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

[hjl.tools at gmail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105506

--- Comment #13 from H.J. Lu <hjl.tools at gmail dot com> ---
Created attachment 54389
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54389&action=edit
A patch for GCC 12 branch

[Bug target/105506] [12/13/14 Regression] Error building GCC 12.1.0 against MinGW-w64: fatal error: cannot execute 'cc1': CreateProcess: No such file or directory

[rguenth at gcc dot gnu.org]

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                        |12.4

--- Comment #14 from Richard Biener <rguenth at gcc dot gnu.org> ---
GCC 12.3 is being released, retargeting bugs to GCC 12.4.