Date: Tue, 19 Mar 1996 17:06:00 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: "Alexander V. Lukyanov" <lav AT video DOT yars DOT free DOT net>
Cc: djgpp AT delorie DOT com
Subject: Re: ./prog - bad command ?
In-Reply-To: <199603181727.UAA05374@video.yars.free.net>
Message-Id: <Pine.SUN.3.91.960319165412.20848K-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Mon, 18 Mar 1996, Alexander V. Lukyanov wrote:

> If I write in makefile ./program to start just compiled program,
> I receive message 'Bad command or file name' from command.com.

Can you post the relevant part of Makefile?  Make does call COMMAND.COM in
certain cases (like when the command line you define in the rule uses
redirection), but it's impossible to say for sure without seeing the
actual rule which your Makefile invokes. 

> Isn't it a bug in the make port? I supposed that make should use
> system() to execute commands, and system() starts my program fine
> without command.com.

`system' from the v2.0 library handles redirection itself, but Make
currently doesn't call `system' when it sees a redirection symbol.  This
isn't as easy to correct as it might seem.  For instance, the current
version of `system' doesn't support long command lines, (without which
redirection support isn't worth much), and DJGPP Make *must* support long
command lines, or you won't be able to compile all the GNU packages. 

(Btw, I'm working on enhancing `system' to do all of the above and then
some, with the explicit goal to use these features in a port of GNU 
Make.  So if you have other complains about the current port of Make, 
drop me a note.)