To: Bill Davidson <bdavidson AT ra DOT isisnet DOT com>
Cc: Tim Freeman <tim AT pi DOT la DOT tce DOT com>, djgpp AT sun DOT soe DOT clarkson DOT edu
Subject: Re: bug in djgpp's make 
Date: Wed, 11 Jan 95 09:15:19 +0200
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>

> sure, but if, for example, you are doing a make with Turbo C and the 
> compiler dies with an error (and let's assume you have set it to 
> compile only, so a command in your make file does the linking) the linker 
> will then be invoked and produce _it's_ error message because the object 
> file isn't present (or worse, and old version of the .obj _is_ present 
> and the linker doesn't complain and you were getting a coffee and don't 
> know the compile is bogus!).  In short, I haven't tried this lately with 
> another make but I am not sure it is a bug, just a gotcha!

Neither bug nor gotcha.  Every reasonable make program calls
compilers directly, not through COMMAND.COM (with spawnXXX()
function call), precisely because this is the only way to get
at its exit status.  GNU Make which comes with DJGPP is no
exception.