Date: Sun, 29 Mar 1998 14:21:35 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Jason A Bennett <jasonb AT gfsmortgage DOT com>
cc: Jason A Bennett <jasonb AT gfsmortgage DOT com>,
        "'djgpp AT delorie DOT com'" <djgpp AT delorie DOT com>
Subject: RE: Make error
In-Reply-To: <01BD5966.1786D310.jasonb@gfsmortgage.com>
Message-ID: <Pine.SUN.3.91.980329142109.15237K-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Fri, 27 Mar 1998, Jason A Bennett wrote:

> The one-line makefile:
> CC = f:\msc\ax\cl
> 
> causes the error.

What happens if you change the Makefile to say this:

     CC = f:/msc/ax/cl

> It seems to run, then nothing.

How do you know it runs at all?  ("Error -1" usually means that Make
didn't find some file, e.g. the compiler it needs to run.)

> D:\pos5\intrface\du\src>make su_du
> f:\msc\ax\cl     su_du.c   -o su_du

This might be a problem: the GNU Make's default rule of how to invoke
a C compiler might not work with MS C compiler.  For example: does it
support the "-o foo" option as meaning ``create a program named
"foo.exe"''?  (Note that there is no explicit .exe extension in the
command issued by Make.)  If not, you might need to define a full
rule, so Make doesn't use its internal database.  For example:

 .c.exe:
	f:/msc/ax/cl -out:$@ $< 

(The above might not be correct, as I don't really know how to invoke
CL.)