From: plugge AT biv7 DOT sr DOT fh-mannheim DOT de (Michel)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Problems using make with included >
Date: 18 Mar 1997 08:26:10 GMT
Organization: Fachhochschule Mannheim - Hochschule fuer Technik und Gestaltung, Germany
Lines: 49
Distribution: world
Message-ID: <5gljj2$44k@noxi.rz.fh-mannheim.de>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 970316155358 DOT 12150U-100000 AT is>
Reply-To: plugge AT biv7 DOT sr DOT fh-mannheim DOT de
NNTP-Posting-Host: axp1.sr.fh-mannheim.de
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp


In article <Pine DOT SUN DOT 3 DOT 91 DOT 970316155358 DOT 12150U-100000 AT is>, Eli Zaretskii
<eliz AT is DOT elta DOT co DOT il> writes:
|>
|>On 14 Mar 1997, Michel wrote:
|>
|>> some days ago I deleted some files on my hard disk, and since that time
|>> I have trouble with makefiles containing the > operator. If I try to
|>> build a targets, I get the error message "no such command or file";
|>> if I rewrite the makefile to circumvent the > operators, the targets are
|>> build right. I know that command.com is used if a > operator is found in
|>> the makefile; but command.com is in its place. Does anyone know, _which_
|>> file actually is not found? Before it worked without any problems.
|>
|>The most probable reason is that you now use a different version of
|>DJGPP and/or Make.  The handling of redirection in Makefiles has
|>changed between DJGPP v2.0 and v2.01, and you seem to experience the
|>adverse effects of that change.  In particular, Make 3.75 does NOT
|>call COMMAND.COM when the Makefile includes redirection, it handles
|>redirection internally.
|>
|>If the above doesn't help you solve the problem, please post some
|>examples of commands from Makefiles which exhibit the problem on your
|>machine.
|>
Sorry that I forgot the system infos. Hardware is Pentium, 32 MB RAM, OS is
W$95,
make 3.73, gcc 2.72.

Yesterday I tried to shorten the makefile, but then the error disappeared. I
think, perhaps the makefile has grown too much, so that some environment space
was too small(???). I'll rewrite the whole stuff to generate a separate makefile
for DOS, and not just use the UNIX makefile, that will save some additional targets.

I tried it already last week, and then I got the error also with minimal makefiles: 
for example,

c2ltx.c: c2ltx.l
	flex -8 -t c2ltx.l > c2ltx.c

fails, but

c2ltx.c: c2ltx.l
	flex -8 -oc2ltx.c c2ltx.l

generates the expected result. Perhaps it is a hidden feature of the W$95 software.

Michel