Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Subject: RE: Similar Bash 3.1.18 CR/LF Problem
Date: Thu, 5 Oct 2006 09:04:17 -0700
Message-ID: <657A9BE009D3504AAE29BD8E8C2DD61E01A5AC3E@SDGEXEVS02.corp.intuit.net>
In-Reply-To: <45246060.9010500@byu.net>
From: "Wilks, Dan" <Dan_Wilks@intuit.com>
To: <cygwin@cygwin.com>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Content-Transfer-Encoding: 8bit

Eric Blake wrote:
> But I'm not sure whether making
> igncr the default in 'bash --posix', aka '/bin/sh', is wise, since
POSIX
> does not permit this behavior.  My only concern is that by making
igncr
> cognizant of whether posix behavior is requested, people will start
asking
> 'why does my script work with #!/bin/bash but not #!/bin/sh?'.

Ugh... If push does come to shove, I guess I can tell the
Windows-centric
folks on the team to set SHELL=c:/cygwin/bin/bash.exe so that the Win32
Version of GNU make will execute "bash c:\temp\tempscript.sh" rather
than
sh.  Just one more thing to get wrong; one more thing for our developer
install sheet; one more faq; one more...  

Seriously though, as long as I can get it to work we'll be happy.

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