X-Spam-Check-By: sourceware.org
Message-ID: <45A7B6A9.76BB7D15@dessent.net>
Date: Fri, 12 Jan 2007 08:26:17 -0800
From: Brian Dessent <brian AT dessent DOT net>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: dos format shell script  executed fine with 1.5.12, fails with   1.5.23
References: <005c01c73664$c5d727f0$300b17ac AT sanmateo DOT corp DOT akamai DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
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

jim wrote:

> I have a dos format file containing a shell script that works fine on
> 1.5.12.   After upgrading to 1.5.23, the script fails.   If I convert it to
> Unix format, it works fine with 1.5.23, but I'm wondering what changed.
> Cygwin mounts are the same; what else could be different?

The version of the Cygwin DLL here is totally irrelevant.  When you
updated the cygwin package you also updated the bash package, and the
change you are seeing is a result of changes in the bash package. 
Please consult the bash package announcement emails.  There have
probably been hundreds of emails in dozens of threads on this particular
issue over the last 6 months or so, so please take a chance to read all
those before bringing up a topic that has been beaten to death, revived,
and then beaten again.

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/