[llvm-commits] [llvm] r94535 [1/3] - in /llvm/trunk: configure include/llvm/Config/config.h.in

[Jeffrey Yasskin]

On Tue, Feb 2, 2010 at 12:42 AM, Török Edwin <edwintorok at gmail.com> wrote:
> On 02/02/2010 07:15 AM, Jeffrey Yasskin wrote:
>> On Tue, Jan 26, 2010 at 1:01 AM, Török Edwin <edwintorok at gmail.com> wrote:
>>
>>> On 01/26/2010 10:50 AM, Torok Edwin wrote:
>>>
>>>> Author: edwin
>>>> Date: Tue Jan 26 02:50:50 2010
>>>> New Revision: 94535
>>>>
>>>> URL: http://llvm.org/viewvc/llvm-project?rev=94535&view=rev
>>>> Log:
>>>> Regenerate configure.
>>>>
>>>> With the previous cleanup to configure.ac, configure is now only 393k, instead of 1.1M!
>>>>
>>>>
>>> configure can be regenerated with both autoconf 2.60 and 2.65 now.
>>>
>>
>> Could you update autoconf/AutoRegen.sh to reflect this?
>>
>> Also, do we want to allow two versions of autoconf, given that it
>> produces rather large diffs in configure?
>>
>
> I think it is a matter of what autoconf people have installed:
> I don't have, and can't install 2.60 in Debian sid (it only has 2.13,
> 2.59, 2.61, 2.64, 2.65).
> If we'd make autoconf 2.65 a requirement then people who were
> using/regenerating configure with autoconf 2.60
> wouldn't have 2.65 installed.
>
> Thus I think we should allow both autoconf versions to be used (locally
> at least).
>
> As for what version is used when comitting to the repository, I agree
> that it should be the same to reduce diffs,
> but I'd rather leave it to someone else to decide which version that
> should be.

I'm going to reconfigure back to autoconf-2.60 since that seems least
likely to break people's existing setups. Edwin, you can install
autoconf-2.60 from source even if your package manager doesn't provide
it. I've set up a ~/bin/llvm_autotools prefix specifically to deal
with AutoRegen.sh's odd version requirements.

If we do want to upgrade to autoconf-2.65, I'd have no objections, but
whoever reconfigures to it should update AutoRegen.sh and the
GettingStarted.html at the same time.