Re: Postgres Windows build system doesn't work with python installedin Program Files - Mailing list pgsql-hackers

From Juan José Santamaría Flecha
Subject Re: Postgres Windows build system doesn't work with python installedin Program Files
Date
Msg-id CAC+AXB0OZrffMBD8MitfvSfN-PakdXFdGgbD1BJvtazeNGsk-Q@mail.gmail.com
Whole thread Raw
In response to Re: Postgres Windows build system doesn't work with python installedin Program Files  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Postgres Windows build system doesn't work with python installedin Program Files
List pgsql-hackers

On Mon, May 4, 2020 at 2:18 PM Michael Paquier <michael@paquier.xyz> wrote:
On Mon, May 04, 2020 at 09:45:54AM +0200, Juan José Santamaría Flecha wrote:
> I think these are two different issues, python PATH and build.pl warnings.
> For the later, you can check woodloose logs and see the warning after
> commit 8f00d84afc.

Oh, indeed.  I somewhat managed to miss these in the logs of the
buildfarm.  What if we refactored the code of build.pl so as we'd
check first if $ARGV[0] is defined or not?  If not defined, then we
need to have a release-quality build for all the components.  How does
that sound?  Something not documented is that using "release" as first
argument enforces also a release-quality build for all the components,
so we had better not break that part.

+1, seems like the way to go to me.

Regards,

Juan José Santamaría Flecha

pgsql-hackers by date:

Previous
From: Juan José Santamaría Flecha
Date:
Subject: Re: PG compilation error with Visual Studio 2015/2017/2019
Next
From: Julien Rouhaud
Date:
Subject: Re: WAL usage calculation patch