Re: PL_stashcache, or, what's our minimum Perl version?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Noah Misch <noah(at)leadboat(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: PL_stashcache, or, what's our minimum Perl version?
Date: 2017-07-31 19:38:10
Message-ID: 14432.1501529890@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> One major PITA with the AC_PATH_* checks is that you can only override
> them with environment variables that are full paths; otherwise the
> environment variables are ignored. For example, currently, running

> ./configure PYTHON=python3

> will result in the PYTHON setting being ignored.

Really? That seems pretty broken, independently of how many variables
are affected. But the ones you'd be most likely to do that with are
using AC_PATH_PROG already, I think. Having lesser-used program variables
behave inconsistently doesn't seem like much of a win.

I'd almost be inclined to say that we should override that behavior
of AC_PATH_PROG. It is undocumented AFAICS, and it's not amazingly
well thought out, either.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2017-07-31 19:48:13 Re: PostgreSQL - Weak DH group
Previous Message Peter Eisentraut 2017-07-31 19:37:25 Re: PL_stashcache, or, what's our minimum Perl version?