-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Ralf Wildenhues on 4/18/2006 1:55 AM: > I'm not the only one to stumble over Cygwin with text mode mounts[1]. > As they prevent a successful generation of config.status, this may > need to be addressed before 2.60, or big warning letters printed to > this extent.
Agreed. As the cygwin bash packager, I just patched the cygwin version of bash[1] so that here-docs are always treated as binary files, even if /tmp was accidentally mounted as text mode, in response to a related query about a libtool failure[2]. Hopefully, that will reduce the number of CFLF line endings from heredocs, and may improve the situation with autoconf on a textmode mount. But it will be a while before I have enough time to actually sit down with a text mode mount and analyze every autoconf failure - it really is much easier to document that on cygwin, only binary mode mounts are guaranteed (and that includes /tmp being mounted as binary, since /bin/sh (aka bash) uses /tmp for heredocs). [1] http://cygwin.com/ml/cygwin/2006-04/msg00423.html [2] http://cygwin.com/ml/cygwin/2006-04/msg00414.html - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] -----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 iD8DBQFEROHR84KuGfSFAYARAkHPAJwOOy9rA8BdQ+LCxPo2h1uTcAw9GgCgyU89 uNXiybMbIjwetWqtQteIIQE= =Qgmh -----END PGP SIGNATURE-----
