[Bug libbacktrace/103011] New: fatal error: process.h: No such file or directory when canadian compile x86_64-w64-mingw32

[Bug libbacktrace/103011] New: fatal error: process.h: No such file or directory when canadian compile x86_64-w64-mingw32

[unlvsur at live dot com]

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

            Bug ID: 103011
           Summary: fatal error: process.h: No such file or directory when
                    canadian compile x86_64-w64-mingw32
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libbacktrace
          Assignee: unassigned at gcc dot gnu.org
          Reporter: unlvsur at live dot com
                CC: ian at gcc dot gnu.org
  Target Milestone: ---

Created attachment 51712
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51712&action=edit
error log

make[2]: Entering directory
'/home/cqwrteur/myhome/gcc_build/x86_64-w64-mingw32/x86_64-w64-mingw32/x86_64-w64-mingw32-host/gcc/libbacktrace'
../../../../../../../gcc/libiberty/pex-unix.c:59:10: fatal error: process.h: No
such file or directory
   59 | #include <process.h>
      |          ^~~~~~~~~~~

[Bug libbacktrace/103011] fatal error: process.h: No such file or directory when canadian compile x86_64-w64-mingw32

[unlvsur at live dot com]

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

cqwrteur <unlvsur at live dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |unlvsur at live dot com

--- Comment #1 from cqwrteur <unlvsur at live dot com> ---
Created attachment 51713
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51713&action=edit
config

[Bug libbacktrace/103011] fatal error: process.h: No such file or directory when canadian compile x86_64-w64-mingw32

[unlvsur at live dot com]

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

--- Comment #2 from cqwrteur <unlvsur at live dot com> ---
Probably because of this that breaks compilation
https://github.com/gcc-mirror/gcc/commit/c3e80a16af287e804b87b8015307085399755cd4#diff-6499efb534d0a9459d3af89fe12f0ee024636b275addb16130c9dbe6c5c3dda9

[Bug libbacktrace/103011] fatal error: process.h: No such file or directory when canadian compile x86_64-w64-mingw32

[unlvsur at live dot com]

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

--- Comment #3 from cqwrteur <unlvsur at live dot com> ---
compilation succeeded when comment out process.h. HAVE_PROCESS_H does not make
sense tbh. Actually #if __has_include(<process.h>) can replace all headers. Are
you trying to support old versions' compilers by not using __has_include guard?

but it is still weird, shouldn't that be pex-win32.h??

[Bug libbacktrace/103011] fatal error: process.h: No such file or directory when canadian compile x86_64-w64-mingw32

[ian at airs dot com]

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

Ian Lance Taylor <ian at airs dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ian at airs dot com

--- Comment #4 from Ian Lance Taylor <ian at airs dot com> ---
I think you are misreading the make output slightly due to the use of the -j
option.  pex-unix.c is not built as part of libbacktrace.  The build is failing
while building build-libiberty.  Changing the component.

[Bug other/103011] fatal error: process.h: No such file or directory when canadian compile x86_64-w64-mingw32

[ian at airs dot com]

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

--- Comment #5 from Ian Lance Taylor <ian at airs dot com> ---
Can you add some output from make without the -j option?  I don't understand
how this error is possible.

[Bug other/103011] fatal error: process.h: No such file or directory when canadian compile x86_64-w64-mingw32

[schwab@linux-m68k.org]

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

--- Comment #6 from Andreas Schwab <schwab@linux-m68k.org> ---
Please attach the file build-x86_64-pc-linux-gnu/libiberty/config.log

[Bug other/103011] fatal error: process.h: No such file or directory when canadian compile x86_64-w64-mingw32

[rguenth at gcc dot gnu.org]

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2021-11-02

[Bug other/103011] fatal error: process.h: No such file or directory when canadian compile x86_64-w64-mingw32

[pexu@gcc-bugzilla.mail.kapsi.fi]

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

Pekka S <pexu@gcc-bugzilla.mail.kapsi.fi> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pexu@gcc-bugzilla.mail.kaps
                   |                            |i.fi

--- Comment #7 from Pekka S <pexu@gcc-bugzilla.mail.kapsi.fi> ---
I have a similar cross compiler setup and I'm seeing this exact issue. 
However, I suspect this is actually due to
https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=84401ce5fb4ecab55decb472b168100e7593e01f.

Looking at `gcc/build-x86_64-linux-gnu/libiberty/config.log'
libiberty/configure uses different compiler/preprocessor for tests;
ac_fn_c_try_compile uses `gcc' (i.e. host) but ac_fn_c_try_cpp (via
ac_fn_c_check_header_preproc, the one which is used for e.g. process.h probing)
uses `x86_64-w64-mingw32-gcc -E' (i.e. target).

This can be also seen from the corresponding
`gcc/build-x86_64-linux-gnu/libiberty/config.cache' where ac_cv_env_CPP_value
and ac_cv_prog_CPP are populated with target preprocessor whereas other are
host programs.

I presume this shouldn't happen since `gcc/build-x86_64-linux-gnu/libiberty' is
being built (its target counterpart `gcc/libiberty' compiles just fine).

[Bug other/103011] fatal error: process.h: No such file or directory when canadian compile x86_64-w64-mingw32

[pexu@gcc-bugzilla.mail.kapsi.fi]

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

--- Comment #8 from Pekka S <pexu@gcc-bugzilla.mail.kapsi.fi> ---
Created attachment 51734
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51734&action=edit
For CPP_FOR_BUILD use $(CC_FOR_BUILD) -E instead of $(CPP).

The problem is that when $(CPP) is not defined it is set to $(CC) -E by default
(by GNU make).  However, CPP_FOR_BUILD shall use CC_FOR_BUILD, not CC.

[Bug other/103011] fatal error: process.h: No such file or directory when canadian compile x86_64-w64-mingw32

[law at gcc dot gnu.org]

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

Jeffrey A. Law <law at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |law at gcc dot gnu.org

--- Comment #9 from Jeffrey A. Law <law at gcc dot gnu.org> ---
Should be fixed on the trunk now.  I forgot to add the PR marker though.

[Bug other/103011] fatal error: process.h: No such file or directory when canadian compile x86_64-w64-mingw32

[pinskia at gcc dot gnu.org]

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |RESOLVED
         Resolution|---                         |FIXED

--- Comment #10 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
.