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

From: Peter Eisentraut <peter_e(at)gmx(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: Buildfarm coverage (was Re: OK, ready for RC1 or Beta6)
Date: 2004-12-03 20:37:42
Message-ID: 200412032137.42690.peter_e@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Where the buildfarm falls down a bit is on the cross-product
> coverage. But I think you're not going to get the cross product
> without a call for port reports; there aren't that many people who
> are going to offer dedicated time on every random platform there is.

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
make
make install
make check

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-12-03 20:54:25 Re: Buildfarm coverage (was Re: OK, ready for RC1 or Beta6)
Previous Message Kenneth Marshall 2004-12-03 20:33:10 Re: Buildfarm coverage (was Re: OK, ready for RC1 or Beta6)