Freebsd & autoconf-2.63

[Ashish-34]

Hi there,


I downloaded the latest postgresql code via cvs on a FreeBSD 7.2 system. When I try to run autoconf on the source it tells me that I need autoconf-2.63. However the freeBSD ports only has autoconf-6.62.

Does anyone have any suggestion on how to resolve this? I posted a question on the freebsd ports forum but have not had any solutions.

Thanks
Ashish







--
Sent via pgsql-hackers mailing list (pgsql-hackers@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

[Heikki Linnakangas-3]

abindra@... wrote:
> I downloaded the latest postgresql code via cvs on a FreeBSD 7.2 system.
> When I try to run autoconf on the source it tells me that I need
> autoconf-2.63. However the freeBSD ports only has autoconf-6.62.
>
> Does anyone have any suggestion on how to resolve this? I posted a
> question on the freebsd ports forum but have not had any solutions.

Go to http://www.gnu.org/software/autoconf/, and download and install  a
newer version of autoconf.

You shouldn't actually need to run autoconf even when building from a
CVS checkout, because we keep the generated "configure" file in CVS as
well. Unless you have edited configure.in, you can just do "./configure;
make install"

--
  Heikki Linnakangas
  EnterpriseDB   http://www.enterprisedb.com

--
Sent via pgsql-hackers mailing list (pgsql-hackers@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

[Tom Lane-2]

abindra@... writes:
> I downloaded the latest postgresql code via cvs on a FreeBSD 7.2 system. When I try to run autoconf on the source it tells me that I need autoconf-2.63. However the freeBSD ports only has autoconf-6.62.

> Does anyone have any suggestion on how to resolve this? I posted a question on the freebsd ports forum but have not had any solutions.

Well, you could grab our nightly tarball instead of pulling from CVS.
Or you could remove the version-check line from configure.in.  The
latter is actually very likely to work, we just don't promise anything
(if it breaks, debugging is your problem not ours).

                        regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

[Ashish-34]

Thank you Heikki!

I am new to unix, and when "make" said I need to configure I just "Assumed" i need to run autoconf. Running configure directly worked.


Thank you for your help.

On Fri, 6 Nov 2009, Heikki Linnakangas wrote:

> abindra@... wrote:
>> I downloaded the latest postgresql code via cvs on a FreeBSD 7.2 system.
>> When I try to run autoconf on the source it tells me that I need
>> autoconf-2.63. However the freeBSD ports only has autoconf-6.62.
>>
>> Does anyone have any suggestion on how to resolve this? I posted a
>> question on the freebsd ports forum but have not had any solutions.
>
> Go to http://www.gnu.org/software/autoconf/, and download and install  a
> newer version of autoconf.
>
> You shouldn't actually need to run autoconf even when building from a
> CVS checkout, because we keep the generated "configure" file in CVS as
> well. Unless you have edited configure.in, you can just do "./configure;
> make install"
>
> --
>  Heikki Linnakangas
>  EnterpriseDB   http://www.enterprisedb.com
>

--
Sent via pgsql-hackers mailing list (pgsql-hackers@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

[Ashish-34]

Thanks Tom. Heikki's suggestion resolved the issue.

On Fri, 6 Nov 2009, Tom Lane wrote:

> abindra@... writes:
>> I downloaded the latest postgresql code via cvs on a FreeBSD 7.2 system. When I try to run autoconf on the source it tells me that I need autoconf-2.63. However the freeBSD ports only has autoconf-6.62.
>
>> Does anyone have any suggestion on how to resolve this? I posted a question on the freebsd ports forum but have not had any solutions.
>
> Well, you could grab our nightly tarball instead of pulling from CVS.
> Or you could remove the version-check line from configure.in.  The
> latter is actually very likely to work, we just don't promise anything
> (if it breaks, debugging is your problem not ours).
>
> regards, tom lane
>

--
Sent via pgsql-hackers mailing list (pgsql-hackers@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers