Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com X-Apparently-From: Message-ID: <3B31D642.6ACDB3C4@yahoo.com> Date: Thu, 21 Jun 2001 07:10:58 -0400 From: Earnie Boyd Reply-To: Cygwin Users X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Cygwin Users Subject: Re: Autoconf's suggestion to use bash as /bin/sh Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Autoconf suggest that so that you can avoid portability issues. All shells are not created equal. Autoconf requires certain assumptions about the functioning of a shell. It does try to work around the issues and version 2.50 does even more to that end. I suppose Cliff Hones had a question and wasn't just posting to be posting and I assume the hidden question to be "Why does Cygwin not use bash as sh?" and that is covered in the FAQ. However, once upon a time a long time ago Cygwin did use bash as sh. It was discovered that scripts and software builds would happen more quickly if ash was used as sh. So the next release of Cygwin after the discovery included ash as sh. This doesn't prevent you from using it now, simply `cp /bin/bash.exe /bin/sh.exe' and you'll be compliant with the autoconf suggestion. However, you would have slowed down the functioning of Cygwin scripts and package builds. -- Earnie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple