From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: autoconf version for back branches? |
Date: | 2006-09-04 01:57:50 |
Message-ID: | 44FB881E.2050004@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>
>> I see that older back branches are still using version 2.53 of autoconf,
>> rather than the 2.59 branch we have updated to for 8.1 and beyond. Does
>> that mean I need to install version 2.53 if I want to update the config
>> on those branches?
>>
>
> Yup. We aren't changing back autoconf versions if we can help it ---
> too much risk of breakage.
>
>
>> If so, fixing the plpython problem I reported
>> recently seems like too much work.
>>
>
> It's not a big problem if you install 'em into private subdirectories,
> eg I have autoconf-2.53 installed with --prefix = /usr/local/autoconf-2.53
> and do
> PATH=/usr/local/autoconf-2.53/bin:$PATH autoconf
> when I need to update back-branch configure scripts.
>
>
>
Ah! Thanks! What had failed for me was just running with
/path/to/old/autoconf - this one works however. Strange that a config
package can't work out where its own installed files are.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-09-04 02:05:54 | Re: pgstattuple extension for indexes |
Previous Message | Christopher Browne | 2006-09-04 01:52:18 | Re: BUG #2600: dblink compile with SSL missing |