Date: Tue, 24 Mar 1998 13:11:51 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Robert Hoehne <robert DOT hoehne AT gmx DOT net>
cc: "Salvador Eduardo Tropea (SET)" <salvador AT inti DOT gov DOT ar>, djgpp AT delorie DOT com,
        pavenis AT laima DOT acad DOT latnet DOT lv
Subject: Re: Building gcc-2.8.1 for DJGPP
In-Reply-To: <35169791.BC0A76AC@gmx.net>
Message-ID: <Pine.SUN.3.91.980324130942.21946F-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Mon, 23 Mar 1998, Robert Hoehne wrote:

> ${CONFIG_SHELL-/bin/sh} ....
> 
> which means, when the variable $CONFIG_SHELL is not set, the
> script tries to run /bin/sh.

This is a standard technique in GNU configure scripts.  IMHO, this 
environment variable should be set automatically by the build procedure.  
I suggest to write a config.bat batch file which sets it to "bash" (no 
need for the explicit path and .exe) and then runs "sh ./configure".  
That's what I usually do in GNU packages I port.