Message-ID: <36337F9D.12147CDB@montana.com>
Date: Sun, 25 Oct 1998 12:44:29 -0700
From: bowman <bowman AT montana DOT com>
X-Mailer: Mozilla 4.5b2 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: djgpp AT delorie DOT com
Subject: Re: Recursive make: portable technique?
References: <Pine DOT SUN DOT 3 DOT 91 DOT 981025194815 DOT 24396O-100000 AT is>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com



Eli Zaretskii wrote:
> 
> DJGPP ports of Make v3.75 and later almost never call COMMAND.COM
> (precisely because it is so dumb).  Instead, they call `system' from
> the library which emulates all COMMAND.COM functionality, inluding
> redirection and the CD command.

I'm really getting confused here. If command.com never sees the cd
command,
in v3.77, what breaks when bash isn't present? Is is just because
Make[2] 
can't be created under command.com? Why so? I've found, more or less
inadvertantly, 
that I can run command.com from MC, create another MC, and another
command.com, and 
back out of them one by one. I'm sure things like environment variable
would be a
royal mess, but the possibility seems to be there.