From: | Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, Victor Wagner <vitus(at)wagner(dot)pp(dot)ru>, 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-07 00:14:16 |
Message-ID: | CAEudQAozeS7m=+vGr-HQPE0+KW5ruqF-WzsxiGB3BG8dqES+tQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Em qua., 6 de mai. de 2020 às 21:08, Michael Paquier <michael(at)paquier(dot)xyz>
escreveu:
> On Wed, May 06, 2020 at 02:11:34PM -0400, Andrew Dunstan wrote:
> > We assume perl, flex and bison are in the PATH. That doesn't seem
> > unreasonable, it's worked well for quite a long time.
>
> I recall that it is an assumption we rely on since MSVC scripts are
> around, and that's rather easy to configure, so it seems to me that
> changing things now would just introduce annoying changes for anybody
> (developers, maintainers) using this stuff.
>
Ah yes, better to leave it as is. No problem for me, I already got around
the difficulty.
regards,
Ranier Vilela
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2020-05-07 00:14:33 | Re: Postgres Windows build system doesn't work with python installed in Program Files |
Previous Message | Michael Paquier | 2020-05-07 00:08:25 | Re: Postgres Windows build system doesn't work with python installed in Program Files |