diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2017-08-01 11:40:00 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2017-08-01 11:40:08 -0400 |
commit | b21c569cea58a1396d9ffd8a7e7a84aa991a1123 (patch) | |
tree | 5240b9abeb9a4c41dcf8ef9b2ea4739ac048059a /src | |
parent | 4de6216877a32e869fe1cf168c1fe1ffb8c3d576 (diff) | |
download | postgresql-b21c569cea58a1396d9ffd8a7e7a84aa991a1123.tar.gz postgresql-b21c569cea58a1396d9ffd8a7e7a84aa991a1123.zip |
Further improve consistency of configure's program searching.
Peter Eisentraut noted that commit 40b9f1921 had broken a configure
behavior that some people might rely on: AC_CHECK_PROGS(FOO,...) will
allow the search to be overridden by specifying a value for FOO on
configure's command line or in its environment, but AC_PATH_PROGS(FOO,...)
accepts such an override only if it's an absolute path. We had worked
around that behavior for some, but not all, of the pre-existing uses
of AC_PATH_PROGS by just skipping the macro altogether when FOO is
already set. Let's standardize on that workaround for all uses of
AC_PATH_PROGS, new and pre-existing, by wrapping AC_PATH_PROGS in a
new macro PGAC_PATH_PROGS. While at it, fix a deficiency of the old
workaround code by making sure we report the setting to configure's log.
Eventually I'd like to improve PGAC_PATH_PROGS so that it converts
non-absolute override inputs to absolute form, eg "PYTHON=python3"
becomes, say, PYTHON = /usr/bin/python3. But that will take some
nontrivial coding so it doesn't seem like a thing to do in late beta.
Discussion: https://postgr.es/m/90a92a7d-938e-507a-3bd7-ecd2b4004689@2ndquadrant.com
Diffstat (limited to 'src')
0 files changed, 0 insertions, 0 deletions