Skip to content
Snippets Groups Projects
Select Git revision
  • benchmark-tools
  • postgres-lambda
  • master default
  • REL9_4_25
  • REL9_5_20
  • REL9_6_16
  • REL_10_11
  • REL_11_6
  • REL_12_1
  • REL_12_0
  • REL_12_RC1
  • REL_12_BETA4
  • REL9_4_24
  • REL9_5_19
  • REL9_6_15
  • REL_10_10
  • REL_11_5
  • REL_12_BETA3
  • REL9_4_23
  • REL9_5_18
  • REL9_6_14
  • REL_10_9
  • REL_11_4
23 results

postgres-lambda-diff

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Tom Lane authored
    Previously we had a mix of uses of AC_CHECK_PROG[S] and AC_PATH_PROG[S].
    The only difference between those macros is that the latter emits the
    full path to the program it finds, eg "/usr/bin/prove", whereas the
    former emits just "prove".  Let's standardize on always emitting the
    full path; this is better for documentation of the build, and it might
    prevent some types of failures if later build steps are done with
    a different PATH setting.
    
    I did not touch the AC_CHECK_PROG[S] calls in ax_pthread.m4 and
    ax_prog_perl_modules.m4.  There seems no need to make those diverge from
    upstream, since we do not record the programs sought by the former, while
    the latter's call to AC_CHECK_PROG(PERL,...) will never be reached.
    
    Discussion: https://postgr.es/m/25937.1501433410@sss.pgh.pa.us
    40b9f192
    History
    Name Last commit Last update