Re: how to handle missing "prove"

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: how to handle missing "prove"
Date: 2014-11-03 21:16:03
Message-ID: 27081.1415049363@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> On 11/3/14 3:11 PM, Tom Lane wrote:
>> If there's a commit that goes with this statement, you neglected to push it...

> Are you not seeing this in configure.in:

> AC_CHECK_PROGS(PROVE, prove)
> if test -z "$PROVE"; then
> AC_MSG_ERROR([prove not found])

Oh, duh. I read your message to mean that you'd just pushed a change
for that, not that it already did it. Nevermind ...

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabrízio de Royes Mello 2014-11-03 21:18:51 Re: Re[2]: [HACKERS] Patch: add recovery_timeout option to control timeout of restore_command nonzero status code
Previous Message Peter Eisentraut 2014-11-03 20:59:00 Re: how to handle missing "prove"