On Fri, 2019-11-15 at 15:52 +0200, Eli Zaretskii wrote:
> Ping! Paul, did you have a chance to look at this issue?
Sorry, I'm quite underwater. I hope to be able to do a bit of make work
over the next few weeks: get out a final RC and a release.
For this, I don't really understand the issue :).
> From: Paul Smith
> Cc: thirdedit...@gmx.net, bug-make@gnu.org
> Date: Tue, 19 Nov 2019 09:22:17 -0500
>
> On Fri, 2019-11-15 at 15:52 +0200, Eli Zaretskii wrote:
> > Ping! Paul, did you have a chance to look at this issue?
>
> Sorry, I'm quite underwater. I hope to be able to do a bit of mak
Follow-up Comment #1, bug #57242 (project make):
Stefan, the behavior you described is intended.
make closes the pipe unless the command has + or (MAKE) or {MAKE}.
This is necessary, because a command can mess up job server operation or a
command may expect a specific fd to be available.
Follow-up Comment #2, bug #57242 (project make):
[comment #1 comment #1:]
> Stefan, the behavior you described is intended.
> make closes the pipe unless the command has + or (MAKE) or {MAKE}.
> This is necessary, because a command can mess up job server operation or a
command may expect a specifi
