Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1deoWU-0001OH-Cb for pgsql-committers@arkaria.postgresql.org; Mon, 07 Aug 2017 20:21:10 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1deoWT-000398-VU for pgsql-committers@arkaria.postgresql.org; Mon, 07 Aug 2017 20:21:10 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1deoWE-0002K7-Ai; Mon, 07 Aug 2017 20:20:54 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1deoW8-0003mb-2I; Mon, 07 Aug 2017 20:20:53 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v77KKkNl012322; Mon, 7 Aug 2017 16:20:46 -0400 From: Tom Lane To: Andrew Dunstan cc: pgsql-committers@postgresql.org, PostgreSQL-development Subject: Re: pgsql: Record full paths of programs sought by "configure". In-reply-to: <51fca142-5ead-7f57-1798-2e02972b27c1@2ndQuadrant.com> References: <7295.1502133694@sss.pgh.pa.us> <90c39664-ec60-77dc-9f1b-21e8fa7b864c@2ndQuadrant.com> <10269.1502134598@sss.pgh.pa.us> <2a8e30d4-d584-1d74-6efa-100112062333@2ndQuadrant.com> <11702.1502136420@sss.pgh.pa.us> <51fca142-5ead-7f57-1798-2e02972b27c1@2ndQuadrant.com> Comments: In-reply-to Andrew Dunstan message dated "Mon, 07 Aug 2017 16:15:11 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <12320.1502137246.1@sss.pgh.pa.us> Date: Mon, 07 Aug 2017 16:20:46 -0400 Message-ID: <12321.1502137246@sss.pgh.pa.us> List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-committers Precedence: bulk Sender: pgsql-committers-owner@postgresql.org Andrew Dunstan writes: > On 08/07/2017 04:07 PM, Tom Lane wrote: >> Sorry, I was imprecise. What I'm suggesting is that you drop the >> runtime PATH-foolery and instead put this in configure's environment: >> >> PROVE=$perlpathdir/prove >> >> Otherwise you're basically lying to configure about what you're going >> to use, and that's always going to break eventually. > Hmm, you're saying this should work now? OK, I'll try it when I get a > minute to spare. I'm pretty sure it's always worked, at least in the sense that you could override what configure would put into Makefile.global that way. I'm not quite clear on whether providing an exact path to "prove" there is enough to fix your problem. If we have any places where we need to invoke the corresponding version of "perl", then we have more things to fix. >> Hm, yeah, the IPC::Run test would need to deal with this as well. >> A PROVE_PERL environment variable is one way. Or maybe simpler, >> just skip the probe for IPC::Run if PROVE has been specified >> externally; assume the user knows what he's doing in that case. > WFM OK, I'll go make that happen. regards, tom lane -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers