Date: Thu, 12 Sep 1996 16:12:06 +0200 (METDST)
From: Robert Hoehne <robert DOT hoehne AT mathematik DOT tu-chemnitz DOT de>
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Cc: djgpp-workers AT delorie DOT com
Subject: Re: Make 3.74 diffs
In-Reply-To: <Pine.SUN.3.91.960912165017.16232D-100000@is>
Message-Id: <Pine.HPP.3.91.960912160412.8310E-100000@newton.mathematik.tu-chemnitz.de>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Thu, 12 Sep 1996, Eli Zaretskii wrote:

> exactly what are you saying.  Can you please elaborate, or give an 
> example of a Makefile that is broken by the way Make works?  I built 
Here is a very simple makefile:

all:
	$(MAKE) test

test:
	echo test

If the $(SHELL) variable is set to $COMSPEC, then a batch-file with
contents like

i:/djgpp.v2/bin/make.exe test

is creatated and executed by command.com. But command.com does not know
about the forward slashes. (The above example is not exactly tested by
me, because I have my DOS-machine at home, but I remember this, when
I debugged make)

Any other command with long commandlines will be also broken, because
command.com truncates them.

And the last reason is the speed.

Robert