Message-ID: <250B3114DA16D511B82C00E0094005F8023FC194@MSGWAW11>
From: Wojciech Galazka <wojciech DOT galazka AT polkomtel DOT com DOT pl>
To: "'Eli Zaretskii'" <eliz AT is DOT elta DOT co DOT il>,
        Wojciech Galazka <wojciech DOT galazka AT polkomtel DOT com DOT pl>
Cc: "'djgpp-workers AT delorie DOT com'" <djgpp-workers AT delorie DOT com>
Subject: RE: W2K error message documentation
Date: Thu, 20 Sep 2001 19:06:24 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Reply-To: djgpp-workers AT delorie DOT com



> -----Original Message-----
> From: Eli Zaretskii [mailto:eliz AT is DOT elta DOT co DOT il]
> 
> On Thu, 20 Sep 2001, Wojciech Galazka wrote:
> > 
> > NTCMDPROMPT
> 
> Are you saying that with this trick, even if Make invokes
> "command.com /c ..." explicitly, Windows will run cmd instead?
> I'd be surprised if it did.
> 
It will not
I think one should assume that command com is not fully LFN-aware on
NT/W2K/XP
The best, perhaps is to rewrite make rules of type 'command.com /c ..'  with
something more portable
Is there any specific reason of such rules at all?

> 
> 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 ...".
> 
This adds unnecessary complexity to a makefile