-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to MS on 5/11/2007 4:30 AM: > its windows based. (i am running W2K, and i tried it on a XP machine too). > at first the problem occured with m4 1.4 and cygwin1.dll from Cygnus 1.1.7.
I _highly_ suggest updating your cygwin installation. Cygwin1.dll is now at 1.5.24, and I maintain the cygwin port of m4, which is at m4 1.4.9. Anything older than that has known bugs, so I am not willing to spend time helping you debug obsolete setups. I also recommend that you ask on the cygwin mailing list (cygwin AT cygwin DOT com) rather than here, since your problem is cygwin-specific. > > a few days ago i installed MSYS1.0 and tried it in this environment with the > same result. I'm less familiar with an MSYS environment, but I know the msys project forked from cygwin, but tends to use mingw binaries. The mingw port of m4 uses Microsoft's stdio instead of cygwin's. I know that Microsoft's stdio is buggy on text files, and am trying to find time to help gnulib work around that, but I don't think the bugs are the same. But are you sure you weren't just using msys as the shell, but still getting the behavior of the cygwin m4? > e:\temp on /tmp type user (textmode) > c: on /cygdrive/c type user (binmode,noumount) Was your input file in /tmp, perchance, since that is your only text mount? I suggest sticking with binary mounts if you are going to use cygwin. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGRF7D84KuGfSFAYARAl5qAJ44aokUSVy7XIzF4WWsvTHyIuQfSQCggwFX mQsYRzD2+Uy7XCaoDkK2Zrw= =wbVq -----END PGP SIGNATURE----- _______________________________________________ Bug-m4 mailing list Bug-m4@gnu.org http://lists.gnu.org/mailman/listinfo/bug-m4
