Re: pgsql: Fix compiler warning for ppoll() on Cygwin

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net>
Subject: Re: pgsql: Fix compiler warning for ppoll() on Cygwin
Date: 2019-12-26 05:41:59
Message-ID: 26099.1577338919@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> I think the config.cache of lorikeet needs to be cleaned, because the
> return type of strerror_r() has changed as a result of this commit, but
> the build farm logs still show the old test result being used from the
> cache.

lorikeet's latest build run appears to have been done without config
cache, and it succeeded, so your guess was correct.

Next question is why the buildfarm client got that wrong. Seems like
its accache logic needs to notice changes in src/template/* as well as
the configure script proper.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Fujii Masao 2019-12-26 06:11:09 pgsql: Add note about how each partition's default value is treated, in
Previous Message Andrew Dunstan 2019-12-25 21:44:39 Re: pgsql: Fix compiler warning for ppoll() on Cygwin