Martin v. Löwis <mar...@v.loewis.de> added the comment: > I did get that message (and got puzzled by it). > I worked around it by reading the file in universal newlines mode and > saving it again.
I believe this has broken part of the configure script. There is an ac_cr variable that is supposed to hold a sole carriage-return character; it now holds a newline character instead. This will break the test whether the system autoconf deals with carriage-return characters correctly, which probably means that it may decide to use awk to do file substitution when it should have been using /bin/sh, or vice versa (I haven't fully understood the purpose of this test). ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue3585> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com