Similar Bash 3.1.18 CR/LF Problem

Eric Blake
Fri Sep 29 02:59:00 GMT 2006

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), contains the
> single line "date; date<cr><lf>"
>    C:> cd temp
>    C:\temp> sh      -- works
>    C:\temp> sh C:/temp/  - fails
>    C:\temp> sh C:\temp\  - 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   
volunteer cygwin bash maintainer
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at
Comment: Using GnuPG with Mozilla -


Unsubscribe info:
Problem reports:

More information about the Cygwin mailing list