Re: pgsql: Fix install program detection

On Thu, Jun 28, 2012 at 12:28 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
>> Excerpts from Peter Eisentraut's message of mié jun 27 14:23:11 -0400 2012:
>>> Fix install program detection
>
>> Member grebe is still failing.
>
> protosciurus and castoroides (Solaris 10, I think same machine with
> different compilers) are not happy either.  Also, the first failure
> on those looks like:
>
> gmake[4]: Leaving directory `/export/home/dpage/pgbuildfarm/castoroides/HEAD/pgsql.17031/src/backend'
> /bin/sh ../../config/install-sh -c -d '/export/home/dpage/pgbuildfarm/castoroides/HEAD/pgsql.17031/src/test/regress/./tmp_check/install/export/home/dpage/pgbuildfarm/castoroides/HEAD/inst/lib'
> m 644  libpgport.a '/export/home/dpage/pgbuildfarm/castoroides/HEAD/pgsql.17031/src/test/regress/./tmp_check/install/export/home/dpage/pgbuildfarm/castoroides/HEAD/inst/lib/libpgport.a'
> gmake[3]: m: Command not found
> gmake[3]: [install] Error 127 (ignored)
>
> which seems bad for another reason: why are we ignoring a command error there?

I'm thinking that $INSTALL or whatever-it-is is getting set to an
empty string. The command was probably intended to be something like
install -m 644 libpgport.a...

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company