Message-Id: <m0yH6n0-000S2xC@inti.gov.ar>
Comments: Authenticated sender is <salvador AT natacha DOT inti DOT gov DOT ar>
From: "Salvador Eduardo Tropea (SET)" <salvador AT inti DOT gov DOT ar>
Organization: INTI
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, Robert Hoehne <robert DOT hoehne AT gmx DOT net>,
        djgpp AT delorie DOT com, pavenis AT laima DOT acad DOT latnet DOT lv
Date: Mon, 23 Mar 1998 10:00:11 +0000
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: Building gcc-2.8.1 for DJGPP
References: <m0yFkZz-000S39C AT inti DOT gov DOT ar>
In-reply-to: <Pine.SUN.3.91.980322154434.12221D-100000@is>
Precedence: bulk

Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:

> 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".

Hmmm... I'm not so sure, perhaps is my installation, perhaps a mistake, but I 
remmeber that I tried to make the link in the bin directory without success.

Greetings, SET
------------------------------------ 0 --------------------------------
Visit my home page: http://set-soft.home.ml.org/
or
http://www.geocities.com/SiliconValley/Vista/6552/
Salvador Eduardo Tropea (SET). (Electronics Engineer)
Alternative e-mail: set-soft AT usa DOT net set AT computer DOT org
CQ: 2951574
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA
TE: +(541) 759 0013