|From:||Michael Paquier <michael(at)paquier(dot)xyz>|
|To:||Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>|
|Cc:||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|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
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:
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 in uc at build.pl line 44.
> Use of uninitialized value $ARGV 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.
|Next Message||Juan José Santamaría Flecha||2020-05-04 07:45:54||Re: Postgres Windows build system doesn't work with python installed in Program Files|
|Previous Message||Michael Paquier||2020-05-04 05:50:22||Re: Rotten parts of src/backend/replication/README|