To: tim AT pi DOT la DOT tce DOT com (Tim Freeman)
Cc: djgpp AT sun DOT soe DOT clarkson DOT edu, opentv AT pi DOT la DOT tce DOT com,
        Stephen Turnbull <turnbull AT shako DOT sk DOT tsukuba DOT ac DOT jp>
Subject: Re: bug in djgpp's make 
Date: Wed, 11 Jan 95 09:07:48 +0200
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>

> I just now fetched oak.oakland.edu:/pub/msdos/djgpp/mak371bn.zip and
> verfied that it has the following bug.  If a makefile contains
>
> foo.o: foo.c
>	asdfasdf < foo.c > foo.o
>	echo hi
>
> and there is a file named foo.c but no executable named asdfasdf, it
> prints
>
> asdfasdf < foo.c > foo.o
> Bad command or file name
> echo hi
> hi
>
> It shouldn't do the echo hi.  Instead, it should stop once an error

Make calls COMMAND.COM whenever it sees redirection in the rule.
COMMAND.COM has a bad habit of not returning non-zero status when
it doesn't find a program to run (seems like from its point of view
all is well...)  Thus Make has no way to know something was wrong.

> By the way, the version of make in pub/msdos/gnuish/gmake371.zip on
> oak.oakland.edu doesn't share this bug.

The only way to do this is to handle redirection without calling
COMMAND.COM.  DJGPP v2.0, I hear, will do this also.