From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
---|---|
To: | Victor Wagner <vitus(at)wagner(dot)pp(dot)ru>, 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 18:11:34 |
Message-ID: | 82d6d953-9694-5e22-48b0-9533b64452f7@2ndQuadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 5/6/20 1:14 PM, Victor Wagner wrote:
> В 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.
>
We assume perl, flex and bison are in the PATH. That doesn't seem
unreasonable, it's worked well for quite a long time.
cheers
andrew
--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Ranier Vilela | 2020-05-06 18:19:00 | Re: Postgres Windows build system doesn't work with python installed in Program Files |
Previous Message | Andrew Dunstan | 2020-05-06 18:06:41 | Re: do {} while (0) nitpick |