[issue6585] configure.in forces specific autoconf version

R. David Murray added the comment: My understanding is that the reason that this particular version of autoconf is required is that newer versions introduce mixed line endings into the generated file, which causes problems with storing it in svn. The introduction of the version check was prompt

[issue6585] configure.in forces specific autoconf version

Antonio Cavallo added the comment: Yes the rebuild does an autoreconf step. -- ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue6585] configure.in forces specific autoconf version

Antoine Pitrou added the comment: Does the check trigger when building Python, or only when rebuilding the configure script itself? I think we ship a prebuilt configure script precisely so that people don't have to care about autoconf versions and the like. -- nosy: +pitrou ___

[issue6585] configure.in forces specific autoconf version

New submission from Antonio Cavallo : Hi, I've seen the code change in /python/trunk/configure.in (rev. 74072): it enforces a specific autoconfig version (2.61) in order to build python. Unfortunately OpenSuSE 11.1 (mainstream at time of writing) has an updated version of autoconf 2.63 (and