X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Bret Weinraub Subject: Re: [ANNOUNCEMENT] Updated: bash-3.2.3-5 Date: Fri, 10 Nov 2006 18:24:10 +0000 (UTC) Lines: 40 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Eric Blake byu.net> writes: > > > A new release of bash, 3.2.3-5, has been promoted to current. This leaves > 3.1-6 as the previous version (and not 3.1-9, since only 3.1-6 will work > if you downgrade cygwin). > > .... complete release message deleted. I've adopted 3.2.3-5 (after previously reverting to 3.1-6) on my test box; since I am trapped in a world where people demand to run scripts with evil DOS line endings on them. I exported SHELLOPTS=igncr in the Windows environment. Big honking hairy underfunded build runs great until it hits a call to /bin/sh, at which point the igncr functionality no longer holds.... causing a tremendous gnashing of metal reminiscent of the roar of Godzilla. Details: bash --version 3.2.3(5)-release sh --version 3.1.17(9)-release sh sh: igncr: invalid option name Is this by design or unintended? -bret -- 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/