Message-ID: <45CE1260.3040102@lbl.gov>
Date: Sat, 10 Feb 2007 10:43:44 -0800
From: "Jim Guojun [VFFS]" <j_guojun AT lbl DOT gov>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050108
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: subroutine error for Cygwin bash 3.2.9(11)-release
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

Yes, that is the problem.
The Cygwin bash should provide a better error message, which should be 
trivial.

Thanks,

On 2/9/07, Matt Wozniski wrote:

    Has anyone seen the same problem?

bash-3.2$ sh -x start.sh
+ $'\r'
: command not found
'tart.sh: line 6: syntax error near unexpected token `
'tart.sh: line 6: `func()
  

The difference between machines is probably in using text mounts vs.
binary mounts.  On the machines where it fails, you have binary mounts
with files with CR/NL line endings.  See the latest `bash' release
notes for an explanation of your options, which basically revolve
around either running your scripts through `d2u' to change the line
endings, setting the `igncr' shell option, or switching to text mode
mounts.


See http://www.cygwin.com/ml/cygwin-announce/2006-12/msg00026.html for
more details.


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