This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: bash 3.1.18 seems seriously broken
- From: Eric Blake <ebb9 at byu dot net>
- To: cygwin at cygwin dot com, lbreyer at cs dot ucsd dot edu
- Date: Wed, 27 Sep 2006 19:02:59 -0600
- Subject: Re: bash 3.1.18 seems seriously broken
- References: <451AEBAE.6000703@cs.ucsd.edu>
-----BEGIN PGP SIGNED MESSAGE-----
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 ebb9@byu.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
iD8DBQFFGx9C84KuGfSFAYARAt46AJ9YMH2+/0ZI1RwCJ43Hagg56tNOfwCfbLl+
r9r5HdMEXMT7irrCNgw5rXg=
=ggzD
-----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/