Re: Postgres Windows build system doesn't work with python installed in Program Files

From: Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Ranier Vilela <ranier(dot)vf(at)gmail(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-04 07:45:54
Message-ID: CAC+AXB0PNhpxXCBnMmp3m=xNhL+h1FcQOmk1QTE-VUyQyonoOw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, May 4, 2020 at 7:58 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:

>
> > 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.

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.

Regards,

Juan José Santamaría Flecha

>
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Oleksandr Shulgin 2020-05-04 08:38:03 Re: do {} while (0) nitpick
Previous Message Michael Paquier 2020-05-04 05:58:28 Re: Postgres Windows build system doesn't work with python installed in Program Files