[Python-Dev] autoconf version (Was: What does this mean?) (original) (raw)
Benjamin Peterson musiccomposition at gmail.com
Sun Nov 30 15:54:53 CET 2008
- Previous message: [Python-Dev] autoconf version (Was: What does this mean?)
- Next message: [Python-Dev] Attribute error: providing type name
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sun, Nov 30, 2008 at 5:22 AM, "Martin v. Löwis" <martin at v.loewis.de> 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 "accr". I've since always asked Benjamin regenerate configure, who seems to have a setup where accr 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."
- Previous message: [Python-Dev] autoconf version (Was: What does this mean?)
- Next message: [Python-Dev] Attribute error: providing type name
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]