From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Davin M(dot) Potts" <davin(at)discontinuity(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
Subject: | Re: [Pgbuildfarm] buildfarm olinguito vs python |
Date: | 2015-05-27 01:51:53 |
Message-ID: | 455.1432691513@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Davin M. Potts" <davin(at)discontinuity(dot)net> writes:
> On Mon, May 25, 2015 at 04:37:11PM -0400, Tom Lane wrote:
>> I'm fairly sure that the errors were blatantly obvious, ie failure to
>> build or failure to pass even basic regression tests. If you can tell
>> us that that configure check is inappropriate on modern openbsd, I'd
>> be happy to see it go.
> With Tom's bit of encouragement, I removed these four lines from the
> config/python.m4 file:
> case $host_os in
> openbsd*)
> AC_MSG_ERROR([threaded Python not supported on this platform])
> ;;
> esac
> [ and it worked ]
Cool.
> Though I have only verified this against HEAD, if this change is made
> across all the active branches, we will see its impact on olinguito's
> buildfarm-builds of those branches too. Or, I can walk through and
> manually test each branch if that's preferred?
I see no need for that; as you say, if it's somehow broken in a back
branch the buildfarm will soon tell us. I will go remove that configure
check.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2015-05-27 01:51:54 | Re: psql po translation update |
Previous Message | Robert Haas | 2015-05-27 01:45:36 | Re: [COMMITTERS] pgsql: Add pg_audit, an auditing extension |