Date: Sun, 2 May 1999 11:17:47 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Salvador Eduardo Tropea (SET)" <salvador AT inti DOT gov DOT ar>
cc: djgpp-workers AT delorie DOT com
Subject: Re: fork/exec/wait -> system .... More problems. CygWin is that bad?
In-Reply-To: <m10cxwW-000S2dC@inti.gov.ar>
Message-ID: <Pine.SUN.3.91.990502111718.563M-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Thu, 29 Apr 1999, Salvador Eduardo Tropea (SET) wrote:

> It looks very strange because according to a post in the Allegro 
> mailing list (problems with makefiles for CygWin) looks like Make uses 
> command.com if no shell is available, but perhaps that's made by
> code in Make and no automatically by system.
>  Anybody knows about it? Eli, you know about make, what's your
> opinion?

The Cygwin version of Make is not yet in the official GNU Make
distribution; DJ told me they have a special internally-maintained
version.

So I don't have any clue about how the Cygwin version solves the shell
schizophrenia.

FWIW, I think that the DJGPP's way of deciding dynamically on what is
the shell and letting the user to make sure `system' gets only
commands that the installed shell can grok, is the best idea.