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

From Michael Paquier
Subject Re: Postgres Windows build system doesn't work with python installedin Program Files
Date
Msg-id 20200504055828.GF471944@paquier.xyz
Whole thread Raw
In response to Re: Postgres Windows build system doesn't work with python installedin Program Files  (Ranier Vilela <ranier.vf@gmail.com>)
Responses Re: Postgres Windows build system doesn't work with python installedin Program Files  (Juan José Santamaría Flecha <juanjo.santamaria@gmail.com>)
Re: Postgres Windows build system doesn't work with python installedin Program Files  (Ranier Vilela <ranier.vf@gmail.com>)
List pgsql-hackers
On Sun, May 03, 2020 at 04:23:24PM -0300, Ranier Vilela wrote:
> I don't know if it applies to the same case, but from the moment I
> installed python on the development machine, the Postgres build stopped
> working correctly.
> Although perl, flex and bison are available in the path, the build does not
> generate files that depend on flex and bison.

Are you following the instructions of the documentation?  Here is a
link to them:
https://www.postgresql.org/docs/devel/install-windows-full.html

My guess is that you would be just missing a PATH configuration or
such because python enforced a new setting?

> Warning from build.pl
> Use of uninitialized value $ARGV[0] in uc at build.pl line 44.
> Use of uninitialized value $ARGV[0] in uc at build.pl line 48.

Hmm.  We have buildfarm machines using the MSVC scripts and Python,
see for example woodloose.  And note that @ARGV would be normally
defined, so your warning looks fishy to me.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Rotten parts of src/backend/replication/README
Next
From: Juan José Santamaría Flecha
Date:
Subject: Re: Postgres Windows build system doesn't work with python installedin Program Files