X-Spam-Check-By: sourceware.org
Message-ID: <45089854.8010705@scytek.de>
Date: Wed, 13 Sep 2006 16:46:28 -0700
From: Volker Quetschke <quetschke AT scytek DOT de>
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: bash-3.1-7　BUG
References: <091320060438 DOT 11140 DOT 45078B490008FD8600002B8422007610640A050E040D0C079D0A AT comcast DOT net> <20060913052510 DOT GB1256 AT trixie DOT casa DOT cgf DOT cx> <loom DOT 20060913T160909-692 AT post DOT gmane DOT org> <ee9oa9$sj$1 AT sea DOT gmane DOT org> <ee9q53$74g$1 AT sea DOT gmane DOT org> <loom DOT 20060913T234039-426 AT post DOT gmane DOT org> <ee9vg0$qeb$1 AT sea DOT gmane DOT org>
In-Reply-To: <ee9vg0$qeb$1@sea.gmane.org>
Content-Type: multipart/signed; micalg=pgp-sha1;  protocol="application/pgp-signature";  boundary="------------enig4E69E5F85BCF4B3D6566A320"
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

--------------enig4E69E5F85BCF4B3D6566A320
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,

mwoehlke wrote:
> Eric Blake wrote:
>> mwoehlke <mwoehlke <at> tibco.com> writes:
(snip)
>> ...  If the scan in binary mode
>> succeeds, then leave the file in binary mode, assuming that the file
>> is unix format even though it is on a text mount, and that lseeks will
>> work.  If the file starts life binary mode (ie. was on a binary
>> mount), skip the check for \r in the scan (under the assumption that
>> on a binary mount, \r is intentional and not a line ending to be
>> collapsed), and use lseeks.  No guarantees on whether this will pan
>> out, or be bigger than I thought, but hopefully you will see a bash
>> 3.1-8 with these semantics soon.
>=20
> Sounds good! That will satisfy my request to not silently work on files
> that should be broken. :-)

I'm seeing the next "make doesn't work anymore with DOS ... feature" coming
up here, only that it is bash this time. Apparently a lot of people use
tools from cygwin to build Windows stuff in a *NIX build environment.

Not many people that just "use" the tools read this ml and therefore
test if their favorite application still builds. It is definitely in the
eye of the beholder if one calls shell scripts that worked so far as broken
just because they have /r/n line endings.

I'll try to build my favorite testcase OpenOffice.org to see if there are s=
ome
shell scripts with "broken" lineendings hidden in this 500MB sourcecode mon=
ster.

On a separate note, both gcc and Microsofts cl.exe don't care about
the lineendings, neither does tcsh, why should bash start to punish the
offenders?

Volker

--=20
PGP/GPG key  (ID: 0x9F8A785D)  available  from  wwwkeys.de.pgp.net
key-fingerprint 550D F17E B082 A3E9 F913  9E53 3D35 C9BA 9F8A 785D


--------------enig4E69E5F85BCF4B3D6566A320
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (MinGW)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFCJhcPTXJup+KeF0RAqAhAKCBgn2rlJkaVZ7AH8dwH/SKvQB7tgCfVh/f
suFEMZLnAqzOXo2qvaC8d00=
=dYLZ
-----END PGP SIGNATURE-----

--------------enig4E69E5F85BCF4B3D6566A320--