Date: Fri, 29 Jun 2001 17:57:21 +0300
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: "Laurynas Biveinis" <lauras AT softhome DOT net>
Message-Id: <6503-Fri29Jun2001175720+0300-eliz@is.elta.co.il>
X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.9
CC: djgpp-workers AT delorie DOT com
In-reply-to: <20010629142316.A205@lauras.lt>
Subject: Re: bash 2.04 build failure?
References: <Pine DOT LNX DOT 4 DOT 10 DOT 10106291114150 DOT 20259-100000 AT acp3bf> <20010629142316 DOT A205 AT lauras DOT lt>
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> From: "Laurynas Biveinis" <lauras AT softhome DOT net>
> Date: Fri, 29 Jun 2001 14:23:16 +0200
> 
> > How about this, then:
> > 
> > * make libc's behaviour steerable by a control variable and document that.
> > 
> > * Bash would then check some environment variable to decide what it
> >   wants to set that control variable to.
> 
> At least this is a minimum everybody agrees on, so I think I'm gonna do
> libc part, if nobody has started working on it yet.

Could we please have a description of what you think you everybody
agrees to, before you start coding?  There were lots of opinions and
suggestions in this thread, and I'm not sure to what we all agreed...

As an example, everybody seemed to be talking about shell scripts
without extensions, but no one mentioned the other extensionless case:
the raw COFF image.  Please note that in general we would like to
avoid running the raw image when there's a .exe program in the same
place, because the raw image is run via go32-v2.