As previously announced I have committed the update to Autoconf 2.59 as
well as updates of mkinstalldirs, install-sh, as well as config.guess
and config.sub. This shouldn't have any immediate functional impact,
except that you can now turn off the autom4te.cache directory (using
~/.autom4te.cfg). Also, someone forgot to update pg_config.h.in after
the Kerberos 4 removal patch (I think), so I fixed that, too.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo@postgresql.org)

Peter Eisentraut <peter_e@gmx.net> writes:
> As previously announced I have committed the update to Autoconf 2.59 as
> well as updates of mkinstalldirs, install-sh, as well as config.guess
> and config.sub.

Are the correct tools also installed on cvs.postgresql.org (ie, will the
right things happen when Marc tries to build a tarball)?

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org

Tom Lane wrote:
> Are the correct tools also installed on cvs.postgresql.org (ie, will
> the right things happen when Marc tries to build a tarball)?

I don't see any autoconf installed there, so the wrong thing would
happen either way. :-) But gnu-autoconf-2.59 is in the FreeBSD ports,
if it's required.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

On Fri, 1 Jul 2005, Peter Eisentraut wrote:

> Tom Lane wrote:
>> Are the correct tools also installed on cvs.postgresql.org (ie, will
>> the right things happen when Marc tries to build a tarball)?
>
> I don't see any autoconf installed there, so the wrong thing would
> happen either way. :-) But gnu-autoconf-2.59 is in the FreeBSD ports,
> if it's required.

Pick your version:

# ls -lt /usr/local/bin/autoconf*
-r-xr-xr-x 1 root wheel 7672 Aug 22 2004 /usr/local/bin/autoconf259
-r-xr-xr-x 1 root wheel 6194 Aug 22 2004 /usr/local/bin/autoconf253
-rwxr-xr-x 1 root wheel 5007 Jul 27 2003 /usr/local/bin/autoconf213

But, we only run those when modifying configure.in and such, and not as
part of any scripts ...

----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend

Marc G. Fournier wrote:
> Pick your version:
>
> # ls -lt /usr/local/bin/autoconf*
> -r-xr-xr-x 1 root wheel 7672 Aug 22 2004
> /usr/local/bin/autoconf259 -r-xr-xr-x 1 root wheel 6194 Aug 22
> 2004 /usr/local/bin/autoconf253 -rwxr-xr-x 1 root wheel 5007 Jul
> 27 2003 /usr/local/bin/autoconf213
>
> But, we only run those when modifying configure.in and such, and not
> as part of any scripts ...

Btw., the FreeBSD ports have autoconf-2.59, which is a version patched
for FreeBSD use, and gnu-autoconf-2.59, which is the unmodified GNU
release, useful for folks like us, cooperating across many operating
systems. Make sure you use the latter one.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

'k, just checked, and we have the FreeBSD one installed, and always have
used in the in the past ... I can install the gnu-* one if you think it
will make a difference though, but I don't believe we've had any problem
reports on any of our past releases ... ?

On Sat, 2 Jul 2005, Peter Eisentraut wrote:

> Marc G. Fournier wrote:
>> Pick your version:
>>
>> # ls -lt /usr/local/bin/autoconf*
>> -r-xr-xr-x 1 root wheel 7672 Aug 22 2004
>> /usr/local/bin/autoconf259 -r-xr-xr-x 1 root wheel 6194 Aug 22
>> 2004 /usr/local/bin/autoconf253 -rwxr-xr-x 1 root wheel 5007 Jul
>> 27 2003 /usr/local/bin/autoconf213
>>
>> But, we only run those when modifying configure.in and such, and not
>> as part of any scripts ...
>
> Btw., the FreeBSD ports have autoconf-2.59, which is a version patched
> for FreeBSD use, and gnu-autoconf-2.59, which is the unmodified GNU
> release, useful for folks like us, cooperating across many operating
> systems. Make sure you use the latter one.
>
> --
> Peter Eisentraut
> http://developer.postgresql.org/~petere/
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
>
>
>

----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

Marc G. Fournier wrote:
> 'k, just checked, and we have the FreeBSD one installed, and always
> have used in the in the past ... I can install the gnu-* one if you
> think it will make a difference though, but I don't believe we've had
> any problem reports on any of our past releases ... ?

I think it is the general understanding that we use GNU Autoconf, not
FreeBSD Autoconf, so the former is the one that should get used. Also,
when the next person who is not using FreeBSD checks in a configure
update, we get useless diffs and divergences that we could happily do
without.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend

Peter Eisentraut wrote:
> Marc G. Fournier wrote:
> > 'k, just checked, and we have the FreeBSD one installed, and always
> > have used in the in the past ... I can install the gnu-* one if you
> > think it will make a difference though, but I don't believe we've had
> > any problem reports on any of our past releases ... ?
>
> I think it is the general understanding that we use GNU Autoconf, not
> FreeBSD Autoconf, so the former is the one that should get used. Also,
> when the next person who is not using FreeBSD checks in a configure
> update, we get useless diffs and divergences that we could happily do
> without.

Does the FreeBSD one actually produce different output? I don't
remember seeing any of that and I am not running FreeBSD.

--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

Bruce Momjian wrote:
> Does the FreeBSD one actually produce different output?

If it did not, why would they bother making a separate package called
"gnu-autoconf" with the note "This port is specifically designed for
developers that want to create cross-platform software distributions on
FreeBSD."?

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

On Sat, 2 Jul 2005, Peter Eisentraut wrote:

> Bruce Momjian wrote:
>> Does the FreeBSD one actually produce different output?
>
> If it did not, why would they bother making a separate package called
> "gnu-autoconf" with the note "This port is specifically designed for
> developers that want to create cross-platform software distributions on
> FreeBSD."?

If it did produce different output, why haven't we noticed it prior to
this? Has there actually *been* a problem that nobody has reported?

----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo@postgresql.org)