Re: Postgres Win32 build broken?

From: Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Postgres Win32 build broken?
Date: 2021-09-01 11:13:06
Message-ID: CAEudQAqbYCGgAGVb_MeHX+sH6YeLfsYjZp7Z+w41+nZUXywHWg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Em ter., 31 de ago. de 2021 às 22:52, Michael Paquier <michael(at)paquier(dot)xyz>
escreveu:

> On Tue, Aug 31, 2021 at 07:49:40PM -0300, Ranier Vilela wrote:
> > I'm not a perl specialist and it seems to me that the Win32 build is
> broken.
> > The Win32 build is still important because of the 32-bit clients still in
> > use.
> > I'm investigating the problem.
>
> Being able to see the command you are using for build.pl, your
> buildenv.pl and/or config.pl, as well as your build dependencies
> should help to know what's wrong.
>
When I build Postgres to post, I basically don't change anything.
Everything is the head's default.
config.pl does not exist
command to build, either on x64 or Win32.
build.bat <enter>

>
> MSVC builds are tested by various buildfarm members on a daily basis,
> and nothing is red. I also have a x86 and x64 configuration with
> VS2015 that prove to work as of HEAD at de1d4fe, FWIW. Now, by
> experience, one could say that N Windows PG developpers finish with at
> least (N+1) different environments. Basically Simon Riggs's theorem
> applied to Windows development..
>
I'm using the latest msvc 2019.
From the error message, there is no Release|x86, but Release|Win32.
But I still haven't found where are setting this "Release|x86"

regards,
Ranier Vilela

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Gustafsson 2021-09-01 11:15:27 Re: postgres_fdw: Handle boolean comparison predicates
Previous Message Daniel Gustafsson 2021-09-01 11:11:45 Re: [PATCH] Partial foreign key updates in referential integrity triggers