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
Message-ID: <42ACF4A2.41F414E6@dessent.net>
Date: Sun, 12 Jun 2005 19:51:14 -0700
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Making /bin/sh == bash.  Has the time come?
References: <20050613021516 DOT 7B9E913C237 AT cgf DOT cx> <20050613024108 DOT GA3739 AT trixie DOT casa DOT cgf DOT cx>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Report: -5.6/5.0 ---- Start SpamAssassin results  	* -3.3 ALL_TRUSTED Did not pass through any untrusted hosts 	* -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% 	*      [score: 0.0000] 	*  0.3 AWL AWL: From: address is in the auto white-list 	---- End SpamAssassin results
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

Christopher Faylor wrote:

> Now I'm confused, too.  I thought the complaints were coming from people
> who used configure.  Maybe they were coming from old configure scripts
> or possibly from makefiles.

I always got the impression that most of those type of complaints were
people that had written a (non-configure) script themselves, under
linux, with /bin/sh as the shebang, and then tried to run it under
Cygwin.

Brian

--
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/