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 20:11:12
Message-ID: 25640.1415045472@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/2/14 11:36 AM, Tom Lane wrote:
>> Committed patch looks good, but should we also add the stanza we discussed
>> in Makefile.global.in concerning defining $(prove) in terms of "missing"
>> if we didn't find it? I think the behavior of HEAD when you ask for
>> --enable-tap-tests but don't have "prove" might be less than ideal.

> configure will now fail when "prove" is not found.

If there's a commit that goes with this statement, you neglected to push it...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2014-11-03 20:29:18 Re: Let's drop two obsolete features which are bear-traps for novices
Previous Message Heikki Linnakangas 2014-11-03 19:58:51 Re: Missing FIN_CRC32 calls in logical replication code