X-Spam-Check-By: sourceware.org
X-SBRS: None
X-IronPort-AV: i="4.09,231,1157353200";     d="scan'208"; a="65265462:sNHT80923794"
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Subject: Similar Bash 3.1.18 CR/LF Problem
Date: Thu, 28 Sep 2006 10:30:06 -0700
Message-ID: <657A9BE009D3504AAE29BD8E8C2DD61E01A5ABD7@SDGEXEVS02.corp.intuit.net>
In-Reply-To: <451B38B5.9000501@cygwin.com>
From: "Wilks, Dan" <Dan_Wilks AT intuit DOT com>
To: <cygwin AT cygwin DOT com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k8SHUIGN024890

Apologies that this is being written the day after without real output.
I'm now at my desk without easy access to the machine in question.
But...

We've been using Cygwin with text-mode mounts for a long time without
any problems.  A new engineer started the other day, installed a
brand-spanking-new cygwin and came to me with problems running a build.
Without going into details of the build system, after a few hours I
discovered that (all examples are from a cmd shell), foo.sh contains the
single line "date; date<cr><lf>"

   C:> cd temp
   C:\temp> sh foo.sh      -- works
   C:\temp> sh C:/temp/foo.sh  - fails
   C:\temp> sh C:\temp\foo.sh  - fails

The failures were of a form where the first command on a line works but
the second generates an error.  Removing the trailing eol on the on-line
shell script allows the scripts to work regardless of how they're
specified on the sh command line.

Sorry, I don't remember trying sh /cygdrive/c/temp/foo.sh but if I did
it also failed because I know the only way I could get it to work was
w/o any path component.

Mounts are as follows...

C:\OE\trunk\rt\bin>mount
C:\cygwin\bin on /usr/bin type system (textmode)
C:\cygwin\lib on /usr/lib type system (textmode)
C:\cygwin on / type system (textmode)
c: on /cygdrive/c type system (textmode,noumount)
h: on /cygdrive/h type system (textmode,noumount)
i: on /cygdrive/i type system (textmode,noumount)
r: on /cygdrive/r type system (textmode,noumount)
s: on /cygdrive/s type system (textmode,noumount)
u: on /cygdrive/u type system (textmode,noumount)

Oh, and when we downloaded just bash 3.1.6(17?) it didn't overwrite the
old sh.

Dan

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