Eric Blake wrote: > It may have one other difference, not shown in the diff. I know that on > cygwin, you can link any program with binmode.o, textmode.o, or automode.o > (provided alongside crt0.o) to force O_BINARY, O_TEXT, or input in O_TEXT > output in O_BINARY. Perhaps part of what makes Chuck's prebuilt m4 > special is that he pulled in one of these extra platform .o files during > the link phase to change the default mode of stdin/stdout and default > behavior of fopen from what you get in a vanilla build. MSYS does ship with a binmode.o but it's practically a no-op. One of the differences between MSYS and Cygwin is that everything is binmode with MSYS: all mounts are binary and I think that even if you call open(file, O_TEXT) it is still opened in binary mode. It does seem to have a working setmode() and ships with a textmode.o which does appear to actually change the default, but I can't imagine anyone using them given that the intent was for textmode to no longer exist -- especially in this case since the patch adds code to explicitly ignore carriage returns in m4. Brian _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
