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
    The check for IPC::Run we added in commit c254970a is useful in simple
    cases, but there are real use-cases where "prove" is coming from a
    different Perl installation than the "perl" we want to use to build.
    In such cases asking whether "perl" knows about IPC::Run is irrelevant
    and can cause an unnecessary configure failure.  Hence, if user has
    specified a value for PROVE, skip the IPC::Run check.  Per discussion
    with Andrew Dunstan.
    
    Discussion: https://postgr.es/m/E1dcE5n-0005Sk-UE@gemulon.postgresql.org
    8014d2af
    History
    Name Last commit Last update