On Sun, Nov 30, 2008 at 5:22 AM, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote: >>> I should point out that it is 'M'odified in my sandbox, but I just ran >>> autoconf (v2.63) to recreate it from a modified configure.in. >> >> Happens for me too. I investigated a bit and found that autoconf inserts a >> literal \r, i.e. chr(13), into the generated configure, and that trips up >> svn. It occurs at the definition of "ac_cr". >> >> I've since always asked Benjamin regenerate configure, who seems to have >> a setup where ac_cr isn't inserted into the generated file. > > For that very reason, we should continue to use autoconf 2.61. Not sure > why Benjamin put in the comment that 2.63 is being used. If you look at > the configure files that Benjamin has checked in, you'll notice that he > has been using 2.61.
I've been trying to find an autoconf that works with all my projects, so when I wrote, that I may have been using 1.63. Anyway, I've updated the comment to say 1.61. -- Cheers, Benjamin Peterson "There's nothing quite as beautiful as an oboe... except a chicken stuck in a vacuum cleaner." _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
