X-Spam-Check-By: sourceware.org
Message-ID: <451C8C05.6070804@byu.net>
Date: Thu, 28 Sep 2006 20:59:17 -0600
From: Eric Blake <ebb9 AT byu DOT net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060909 Thunderbird/1.5.0.7 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Similar Bash 3.1.18 CR/LF Problem
References: <657A9BE009D3504AAE29BD8E8C2DD61E01A5ABD7 AT SDGEXEVS02 DOT corp DOT intuit DOT net>
In-Reply-To: <657A9BE009D3504AAE29BD8E8C2DD61E01A5ABD7@SDGEXEVS02.corp.intuit.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

*There is NO bash 3.1.18* - just 3.1.17 release 8

According to Wilks, Dan on 9/28/2006 11:30 AM:
> 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.

Sounds like the \r is being interpreted literally.  Use POSIX paths, not
Windows paths, if you want your mount point settings to be honored.

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

Get your versions right.  That would be bash 3.1.17 release 6.

The bash postinstall script is designed for upgrades only.  If /bin/sh is
newer in timestamp than the newly installed /bin/bash, no upgrade occurs.
 This is a feature.  However, it makes downgrades a little awkward.  To
successfully downgrade, you need to manually 'cp /bin/bash.exe /bin/sh.exe'.

- --
Life is short - so eat dessert first!

Eric Blake             ebb9 AT byu DOT net
volunteer cygwin bash maintainer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFHIwE84KuGfSFAYARAv+kAJ9v/8vLVWzSPMIyVG8DNDIkj029kACg0/b5
2LYcIxc6xmZ08EpX0lg+T44=
=UTDB
-----END PGP SIGNATURE-----

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