Date: Mon, 23 Mar 1998 13:23:56 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Andris Pavenis <pavenis AT latnet DOT lv>
cc: Robert Hoehne <robert DOT hoehne AT gmx DOT net>,
        "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: <Pine.GSO.3.96.980323101038.7396A-100000@sisenis>
Message-ID: <Pine.SUN.3.91.980323131715.1968K-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Mon, 23 Mar 1998, Andris Pavenis wrote:
> 1) edit configure and replace CONFIG_SHELL=/bin/sh to /djgpp/bin/sh.exe
>    I'm not very like this way.

The correct way (IMHO) is to set CONFIG_SHELL=bash in the environment 
before running the configure script.  I usually arrange for the 
DJGPP-specific configure.bat to do that before it calls "sh ./configure".  
This way, things are set up for everybody in a transparent way.

> So I prefer one suggested by Robert (2)
> 2) have sh.exe in /bin

IMHO, this is a bad idea.  It means that you need to have /bin/sh.exe on
every drive of your system, or else things will break some day (e.g., if
the script chdirs to another drive).  It also means that you request
people who build the package to do that also. 

DJGPP has a lot of magic designed specifically to alleviate the pains of
working on MS platforms.  Having a /bin directory full of programs on
every drive is one of these annoying things.  I suggest that instead of
going back to these annoying solutions we add features along these lines,
where the current features are not enough.  Let's make it *easier* to
build Unix programs, not *harder*.