From:	"Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
To:	<djgpp-workers AT delorie DOT com>,
	"'Wojciech Galazka'" <wojciech DOT galazka AT polkomtel DOT com DOT pl>
Cc:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Subject:	Re: W2K error message documentation
Date:	Thu, 20 Sep 2001 18:30:33 +0200
Message-ID:	<000501c141f1$943e01e0$33f8e0d5@pandora.be>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook, Build 10.0.2627
In-Reply-To:	<Pine.SUN.3.91.1010920173729.7799A-100000@is>
Importance:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4807.1700
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> The original problem was with a Makefile that invoked command.com
> like shown above.  That Makefile does that because the command
> it wants to run is non-portable to other shells.

So this is a makefile with

SHELL = /bin/sh

but with a certain rule like

foo: bar
	command.com /c some_DOS_only_command

?

> When I said that we will need to find a way to run cmd on those
> systems, I meant the following: we need a method to detect such
> a system from the Makefile, and then run "cmd.exe /c ..." instead
> of "command.com /c ...".

Since we can fairly easily detect NT/2K/XP (right?), couldn't make
substitute '\1cmd.exe /c' for '^\([-@]*\)command\(.com\)? /c'
unconditionally in commands?  That only leaves more complicated
rules (eg some sh-based if-then-else that invokes command.com at
some point) without handling; even those could be handled by
substituting everywhere in a command instead of just the start
(though that might break things somewhere).

- Raw text -