Enabling the jobserver

2024-06-10 Thread Richard Copley
What is the correct way to cause jobserver information to be passed to child processes? I tried this Makefile: all: @echo Jobserver present? $(filter jobserver,$(.FEATURES)) +@sh -c "echo \"make toplevel MAKEFLAGS=${MAKEFLAGS}\"" +@sh -c "echo \"child toplevel MAKEFLAGS=$${MAKEFLAGS}\"

Re: Enabling the jobserver

2024-06-10 Thread Richard Copley
> If you provide a limit you'll see different behavior, e.g.: > > make -j5 I see, thank you. It might not hurt to mention this in the manual, obvious though it may seem. Having passed that hurdle, I see that GCC does not handle the named-semaphore jobserver in native GNU Make on Windows. (I had

Re: Enabling the jobserver

2024-06-11 Thread Richard Copley
On Tue, 11 Jun 2024 at 07:31, Eli Zaretskii wrote: > > > From: Richard Copley > > Date: Mon, 10 Jun 2024 23:29:28 +0100 > > Cc: help-make@gnu.org > > > > Having passed that hurdle, I see that GCC does not handle the > > named-semaphore jobserver in native

Re: Enabling the jobserver

2024-06-11 Thread Richard Copley
On Tue, 11 Jun 2024 at 09:30, Richard Copley wrote: > > On Tue, 11 Jun 2024 at 07:31, Eli Zaretskii wrote: > > (Since you say "GCC source", I presume you are not talking about the > > GCC build scripts, but GCC itself.) Yes, I'm using GCC and GNU Make to b

Re: Enabling the jobserver

2024-06-11 Thread Richard Copley
On Tue, 11 Jun 2024 at 09:55, Eli Zaretskii wrote: > Thanks. I wonder how they distinguish between MinGW (a.k.a. "native") > port of GNU Make, and MSYS/Cygwin ports. The latter implement the > jobserver and the associated command-line arguments as on Unix. > Distinguishing only by name is danger