Message-Id:	<200506130137.j5D1bVVY014364@delorie.com>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	"Gary R. Van Sickle" <g DOT r DOT vansickle AT worldnet DOT att DOT net>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: Making /bin/sh == bash. Has the time come?
Date:	Sun, 12 Jun 2005 20:38:20 -0500
MIME-Version:	1.0
In-Reply-To:	<004701c56f79$1eb791c0$d119fea9@pcdahl4201>
X-IsSubscribed:	yes

> Are you sure you didn't actually measure bash's performance twice?
> If you simply run configure with ash, it will effectively do an
> 
>     exec /bin/bash "$0" "$@"
> 
> at the beginning, unless you force it to stick with ash by 
> setting CONFIG_SHELL=/bin/sh.
> 
> FWIW, I did find that the configure scripts I tested ran 
> faster under ash than under bash, but only by 4% to 8%.
> 
> Regards
> Thorsten Dahlheimer

Wait... So everybody's *always* been using bash during configures?

-- 
Gary R. Van Sickle


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -