From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
Cc: | Victor Wagner <vitus(at)wagner(dot)pp(dot)ru>, Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>, 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:08:25 |
Message-ID: | 20200507000825.GB11539@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Ranier Vilela | 2020-05-07 00:14:16 | Re: Postgres Windows build system doesn't work with python installed in Program Files |
Previous Message | Bruce Momjian | 2020-05-06 23:46:52 | Re: PG 13 release notes, first draft |