Re: Postgres Windows build system doesn't work with python installed in Program Files

From: Victor Wagner <vitus(at)wagner(dot)pp(dot)ru>
To: Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Postgres Windows build system doesn't work with python installed in Program Files
Date: 2020-05-06 17:14:22
Message-ID: 20200506201422.01bc31ab@antares.wagner.home
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

В Wed, 6 May 2020 10:21:41 -0300
Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> пишет:

> Em qua., 6 de mai. de 2020 às 09:53, Michael Paquier
> <michael(at)paquier(dot)xyz> escreveu:
>
> > On Tue, May 05, 2020 at 10:16:23AM +0300, Victor Wagner wrote:
> > > I agree, it is better.
> >
> > Thanks, applied and back-patched down to 9.5. Now for the second
> > problem of this thread..
> >
> Sorry, no clue yet.
> I hacked the perl sources, to hardcoded perl, bison and flex with
> path.It works like this.

Perl has "magic" variable $^X which expands to full path to perl
executable, I wonder why build.pl doesn't use it to invoke secondary
perl scripts.

--

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Juan José Santamaría Flecha 2020-05-06 17:30:50 Re: PG compilation error with Visual Studio 2015/2017/2019
Previous Message Alvaro Herrera 2020-05-06 17:02:26 Re: DROP OWNED CASCADE vs Temp tables