-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Roger While on 5/20/2009 8:38 AM: > A configure genned with 2.63 (on a Linux system) always > terminates with "Could not make config.status" under Cygwin. > Also happens with 2.63b. It works just fine for me on cygwin (in fact, I prepared the autoconf 2.63 release, which includes a self-generated configure file, on a cygwin system). So I wonder if your problem stems from using text mounts instead of binary mounts, where the changed handling of extra ^M by some, but not all, of the tools involved during the configure run is at fault. - -- Don't work too hard, make some time for fun as well! Eric Blake ebb9@xxxxxxx -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkoUpMMACgkQ84KuGfSFAYDYlwCgqX78NXyzp9aKFHdWgbv4elIn 7WwAoNlME9C29aOh/VHfcfxSPvkIqxio =XLpI -----END PGP SIGNATURE----- _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
