bash 3.1.18 seems seriously broken

Eric Blake
Thu Sep 28 01:02:00 GMT 2006

Hash: SHA1

According to Larry Breyer on 9/27/2006 3:22 PM:
> What changed from bash 3.1.17 to 3.1.18 ?

I don't know, but let me know when you find out :)
(There is no 3.1.18 - the latest official bash is 3.1.17, at cygwin
release 8, but upstream is very unlikely to release 3.1.18 since 3.2 is in
beta now.)

> I blindly performed a cygwin update, rebooted, and attempted startx.
> X came up OK but the terminals would not respond to keyboard input.
> Looking at the output of startx it became apparent something was
> seriously wrong with /bin/sh (/bin/bash).
> I got syntax errors on blank lines.

That means your script has CRLF line endings, but resides on a binary
mount point.  Fix it in one of three ways:
change the script to use plain LF line endings (with d2u)
change to a text mount point (with mount)
change the script to ignore whitespace (make the first non-comment line
set IFS appropriately, as in this snippet:
IFS=' ''	''
that would be space, tab, then either CRLF or LF depending on whether your
script is on a binary or text mount)

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