Re: Buildfarm coverage (was Re: OK, ready for RC1 or Beta6)

From: Kurt Roeckx <Q(at)ping(dot)be>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Buildfarm coverage (was Re: OK, ready for RC1 or Beta6)
Date: 2004-12-04 11:50:56
Message-ID: 20041204115055.GA28090@ping.be
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Dec 03, 2004 at 09:37:42PM +0100, Peter Eisentraut wrote:
>
> Once RC1 is out and the build farm has picked it up, we should start
> filling out our little table with the build farm results and then look
> for ways to fill the holes. Does the build farm turn on all the
> compiler options? It really should. I'm looking for
>
> /configure --prefix=SOMEWHERE --enable-thread-safety --with-tcl \
> --with-perl --with-python --with-krb5 --with-pam -with-openssl

I actually run panda (x86_64/amd64) with those options together with
--enable-nls and --enable-integer-datetimes. I based my options
on the debian postgresql package.

Kurt

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2004-12-04 17:08:19 WIN1252 encoding - backend or not?
Previous Message Riccardo G. Facchini 2004-12-04 09:52:19 Re: somebody working on: Prevent default re-use of sysids for dropped users and groups?