Date: Sun, 23 May 1999 12:23:53 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Mark E." <snowball3 AT bigfoot DOT com>
cc: DJGPP-WORKERS <djgpp-workers AT delorie DOT com>
Subject: Re: Bash 2.03 final beta available
In-Reply-To: <199905221457.OAA124424@out2.ibm.net>
Message-ID: <Pine.SUN.3.91.990523122339.26578G-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sat, 22 May 1999, Mark E. wrote:

> > 2. ./configure seems to be wanting to use "getconf". Do you see this
> >    too? What is "getconf"?
> 
> Your seeing this because bash 1.147 always returns 0 for commands 
> executed in a subshell. This is fixed in 2.03.

It might be a good idea to make sure that Bash 2.03 can be configured
and built with Bash 1.14.7, otherwise people might have a bootstraping
problem.  See my other mail about solving the getconf problem with
Bash 1.14.7; that solution should be harmless for Bash 2.03.