> From: John Freeman
> Date: Sat, 4 Sep 2021 17:32:05 -0500
> Cc: make-w32@gnu.org
>
> It's not documented because the details are complex and hard to
> explain, and the result isn't supposed to depend on whether Make
> invokes commands directly or via the shell. So why do you care to
> know
On Sat, Sep 4, 2021 at 12:13 PM Eli Zaretskii wrote:
> It's not documented because the details are complex and hard to
> explain, and the result isn't supposed to depend on whether Make
> invokes commands directly or via the shell. So why do you care to
> know which way does make invoke a given
> From: John Freeman
> Date: Sat, 4 Sep 2021 11:33:01 -0500
> Cc: make-w32@gnu.org
>
> I have since discovered [this
> thread](https://lists.gnu.org/archive/html/make-w32/2020-05/msg1.html),
> the very previous thread on this mailing list, working through the exact same
> problem. I'm happy
On Sat, Sep 4, 2021 at 10:46 AM Eli Zaretskii wrote:
> GNU Make avoids calling the shell for commands that don't require any
> shell functionality it knows about. This is how GNU Make works on all
> platforms, and the Windows port doesn't change that. So if you don't
> have ls.exe or ls.bat or
> From: John Freeman
> Date: Sat, 4 Sep 2021 10:11:19 -0500
>
> I previously sent this message to Eli Zaretskii, whose [EZWinPorts]
> (https://sourceforge.net/projects/ezwinports/files/) binary I am using. He
> asked me to move this conversation
> here.
Thanks for taking it here, this is the ri
I previously sent this message to Eli Zaretskii, whose [EZWinPorts](
https://sourceforge.net/projects/ezwinports/files/) binary I am using. He
asked me to move this conversation here.
I'm trying to choose the shell for my Makefile recipes when I run
EZWinPorts's Windows port of Make 4.3 (without G
