From: Tom Lane <tgl@sss.pgh.pa.us>
To: Noah Misch <noah@leadboat.com>
cc: Andrew Dunstan <andrew@dunslane.net>, pgsql-hackers@postgreSQL.org
Subject: Re: PL_stashcache, or, what's our minimum Perl version?
In-reply-to: <20170730154814.GA2636941@rfd.leadboat.com>
References: <20540.1501210115@sss.pgh.pa.us> <16894.1501392088@sss.pgh.pa.us>
 <20170730154814.GA2636941@rfd.leadboat.com>
Comments: In-reply-to Noah Misch <noah@leadboat.com>
	message dated "Sun, 30 Jul 2017 08:48:14 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <22743.1501430710.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sun, 30 Jul 2017 12:05:10 -0400
Message-ID: <22744.1501430710@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

Noah Misch <noah@leadboat.com> writes:
> On Sun, Jul 30, 2017 at 01:21:28AM -0400, Tom Lane wrote:
>> I think it'd be a good idea to insist that "prove" be in
>> the same directory we found "perl" in.

> Nah; on my machines, I use /usr/bin/perl and ~/sw/cpan/bin/prove.  The la=
tter
> is built against the former, so there's no particular hazard.

Well, OK, but I'd still like to tweak configure so that it records
an absolute path for prove rather than just setting PROVE=3Dprove.
That way you'd at least be able to tell from the configure log
whether you are possibly at risk.

			regards, tom lane


--=20
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers