https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81797
--- Comment #28 from Marc Glisse <glisse at gcc dot gnu.org> ---
I am also failing to see how this can happen without a bug in make or macos.
The failing command is the recipe for ${pch1b_output}. That rule has
${allstamped} as a dependency, which includes stamp-bits-sup, whose recipe does
link the header. At least, disabling precompiled headers should work around it
(--disable-libstdcxx-pch IIRC)
You could always remove the @ sign on the $(STAMP) lines (and the ones before)
so it gets printed in the output, maybe that would show something suspicious.
If you are building in a clean directory (the headers aren't there yet), you
could also remove '-' at the beginning of the $(LN_S) lines, to make sure that
no error occurs. Running make in verbose mode might also hint at something.
Maybe print the date in the pch rule (or use the creation date of
${pch1_output_builddir}), and compare it to the creation date of the symlinks,
etc.
If the issue was with make, you could try replacing
all-local: ${allstamped} ${allcreated}
with
all-local:
$(MAKE) ${allstamped}
$(MAKE) ${allcreated}
Generally, I don't understand why we are linking sources in the build directory
instead of passing -I flags pointing directly to the source directory.
