Re: Non-portable shell code in pg_upgrade tap tests
| От | Tom Lane |
|---|---|
| Тема | Re: Non-portable shell code in pg_upgrade tap tests |
| Дата | |
| Msg-id | 24717.1532285631@sss.pgh.pa.us обсуждение |
| Ответ на | Re: Non-portable shell code in pg_upgrade tap tests (Noah Misch <noah@leadboat.com>) |
| Ответы |
Re: Non-portable shell code in pg_upgrade tap tests
Re: Non-portable shell code in pg_upgrade tap tests |
| Список | 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 по дате отправления: