Re: Non-portable shell code in pg_upgrade tap tests - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Non-portable shell code in pg_upgrade tap tests
Date
Msg-id 24717.1532285631@sss.pgh.pa.us
Whole thread Raw
In response to Re: Non-portable shell code in pg_upgrade tap tests  (Noah Misch <noah@leadboat.com>)
Responses Re: Non-portable shell code in pg_upgrade tap tests  (Michael Paquier <michael@paquier.xyz>)
Re: Non-portable shell code in pg_upgrade tap tests  (Noah Misch <noah@leadboat.com>)
List pgsql-hackers
Noah Misch <noah@leadboat.com> writes:
> On Sun, Jul 22, 2018 at 10:46:03AM -0400, Tom Lane wrote:
>> The pg_upgrade makefile does in fact use $(SHELL), so it will default to
>> whatever shell configure used.

> It will not, because we don't set $(SHELL) anywhere.  $(SHELL) is not @SHELL@.
> In our makefiles, $(SHELL) is always /bin/sh, the GNU make default.

Oh!  Hm, I wonder whether we shouldn't do that, ie add SHELL = @SHELL@
to Makefile.global.in.

A quick trawl of the buildfarm logs says most of our animals compute
SHELL = /bin/sh anyway, and so would be unaffected.  There's a sizable
population that find /bin/bash though, and one active critter that finds
/bin/ksh.

            regards, tom lane


pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: JIT breaks PostGIS
Next
From: Christoph Berg
Date:
Subject: Re: JIT breaks PostGIS