From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Python versions (was Re: RHEL 8.0 build) |
Date: | 2019-01-16 09:15:11 |
Message-ID: | 701bb2e6-1caf-46fe-afdb-42edf73408eb@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 07/01/2019 00:16, Tom Lane wrote:
> BTW, this is a pre-existing problem not the fault of this patch,
> but while we're fooling with the behavior of python lookup would
> be a great time to fix it: we should add something like
>
> AC_ARG_VAR([PYTHON], [path to Python executable])
>
> Aside from improving the "configure --help" documentation, this
> will prevent insane results from using inapplicable cached
> conclusions about what Python we've got. Since more and more
> people seem to be using configure cache files, I think we need
> to be more careful about declaring relevant variables.
Patch attached.
I went through the environment variables listed in installation.sgml and
came up with the following that would affect subsequent cacheable tests:
MSGFMT
PERL
PYTHON
TCLSH
The following are listed but don't affect any other tests, so I didn't
include them:
BISON
DTRACE
DTRACEFLAGS
FLEX
XML2_CONFIG
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Attachment | Content-Type | Size |
---|---|---|
0001-configure-More-use-of-AC_ARG_VAR.patch | text/plain | 3.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Etsuro Fujita | 2019-01-16 11:21:32 | Re: Query with high planning time at version 11.1 compared versions 10.5 and 11.0 |
Previous Message | Masahiko Sawada | 2019-01-16 09:09:56 | Re: Log a sample of transactions |