Date: Sun, 22 Mar 1998 15:44:56 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: "Salvador Eduardo Tropea (SET)" <salvador AT inti DOT gov DOT ar>
cc: Robert Hoehne <robert DOT hoehne AT gmx DOT net>, 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: <m0yFkZz-000S39C@inti.gov.ar>
Message-ID: <Pine.SUN.3.91.980322154434.12221D-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Thu, 19 Mar 1998, Salvador Eduardo Tropea (SET) wrote:

> > This is needed only, if you don't have a /bin/sh.exe on the
> > drive, where you build gcc. So created that and you don't need
> > to modify the Makefile.
> 
> I did a similar thing, in my system I have sh.exe as a "symlink" of
> bash.exe in the /bin directory. Isn't pretty but helps a lot.

You do NOT need sh.exe in /bin, you can have it in *any* directory on
your PATH.  Both Make and Bash will find it and invoke it whenever a
script or a Makefile calls for "/bin/sh".