Eli Zaretskii wrote:
I don't know who benefits from it but so far nobody dared to
document it, either.
I'm not sure it should be documented: the Windows port just behaves
the same as the Unix original. Here's the relevant fragment executed
by Make on Unix (job.c, around line 2100):
# if
> From: "grischka" <[EMAIL PROTECTED]>
> Date: Fri, 19 Oct 2007 19:55:54 +0200
> Cc: make-w32@gnu.org
>
> It is one of gmake's undocumented non-features with SHELL on
> windows.
I always wonder why people feel a need to post such derogatory
comments. Is there some kind of satisfaction in it?
>
Gary Turner wrote:
> It all worked perfectly until I installed a compiler that put a sh
> shell on my path. Since then all my makefiles are broken.
It is one of gmake's undocumented non-features with SHELL on
windows. I don't know who benefits from it but so far nobody
dared to document it, e
> Date: Fri, 19 Oct 2007 07:28:31 -0400
> From: Earnie Boyd <[EMAIL PROTECTED]>
>
> > Make appears to insist on using the sh shell buried on my path rather
> > than cmd.exe
> > I've tried explicitly putting SHELL = cmd.exe in my makefiles - but
> > that didn't seem to work. Putting SHELL = c:\wi
> -Original Message-
> From: make-w32-bounces On Behalf Of Earnie Boyd
> Quoting Gary Turner <[EMAIL PROTECTED]>:
> > It all worked perfectly until I installed a compiler that put a sh
> > shell on my path. Since then all my makefiles are broken.
> Bad business. Is there a reason the c
> Date: Fri, 19 Oct 2007 14:05:23 +1300
> From: Gary Turner <[EMAIL PROTECTED]>
>
> It all worked perfectly until I installed a compiler that put a sh shell
> on my path. Since then all my makefiles are broken.
If your makefiles use features specific to cmd.exe, and don't specify
SHELL = cmd.exe,
Quoting Gary Turner <[EMAIL PROTECTED]>:
It all worked perfectly until I installed a compiler that put a sh
shell on my path. Since then all my makefiles are broken.
Bad business. Is there a reason the compiler needs the PATH set?
Make appears to insist on using the sh shell buried on my
I've used make on windows for quite a while - I use it for all sorts of
non-compilation tasks, and my makefiles tend to occasionally use dos-type
commands - e.g if exist ...
It all worked perfectly until I installed a compiler that put a sh shell on my
path. Since then all my makefiles are brok
