Mail Archives: djgpp/1995/01/11/00:54:23
> It shouldn't do the echo hi. Instead, it should stop once an error
> happens. In general, when there's a DOS command that redirects
> standard input or output in the makefile, and that command gets an
> error, it continues the make, and the error probably goes unnoticed.
>
>Does this depend on the shell being used? When DJGPP make encounters
>a redirection or the like, it passes the command line to the shell. I
>*assume* (but can't verify at the moment, I'm on Linux :) that shells
>(including COMMAND.COM) return a useful exit status, but....
You, of all people, make such an assumption? Command.com, AFAIK, may
not even be smart enough to return a nonzero exit code if it's the
guilty party (e.g. somebody types "proggy < foo" when foo doesn't
exist). I believe 4dos may be sufficiently intelligent (it even
globs properly!) to return a nonzero status in the scenario command.com
fails to handle properly.
> By the way, the version of make in pub/msdos/gnuish/gmake371.zip on
> oak.oakland.edu doesn't share this bug.
>
>I seem to recall that gnuish make ca. ver. 2.5 used to contain code do
>redirections itself. That's why I wonder if the secondary shell used
>by DJGPP make is returning a proper exit status.
Given that datum, command.com is guilty beyond a reasonable doubt.
--- Aaron Ucko (ucko AT vax1 DOT rockhurst DOT edu; finger for PGP public key) -=- httyp!
-=*=-Just because you're paranoid doesn't mean they aren't out to get you.-=*=-
Geek code 2.1 [finger hayden AT vax1 DOT mankato DOT msus DOT edu for explanation]:
GCS/M/S d(-) H s g+ p? !au a-- w+ v+ C++(+++)>++++ UL++(-)(S+)>++++ P++
L+(++) 3(-) E-(----) !N>++ K- W-(---) M-(--) V(--) po-(--) Y+(++) t(+) !5 j R
G tv--(-) b+++ !D(--) B--(---) e>++++(*) u++(@) h!() f(+) r-(--)>+++ n+(-) y?
- Raw text -