X-Spam-Check-By: sourceware.org Message-ID: <17393e3e0702082250m5e14b8cfhd00ea5f01259ac9d@mail.gmail.com> Date: Fri, 9 Feb 2007 01:50:28 -0500 From: "Matt Wozniski" To: cygwin AT cygwin DOT com Subject: Re: subroutine error for Cygwin bash 3.2.9(11)-release In-Reply-To: <45CC0D10.3040306@lbl.gov> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <45CC0D10 DOT 3040306 AT lbl DOT gov> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On 2/9/07, Jim Guojun 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/