MIME-Version: 1.0
References: <CADK3HHLRWj5pXZjLJNw-OHuak9mJ2gTFyB+RpzjNhu4G07kz6Q@mail.gmail.com>
 <20240320211133.pi2sq63xnrz72j6h@awork3.anarazel.de> <CADK3HH+D0O5A00vGsurCs_xu02F_ad2z6mTRk=6mEvWb5DK6Mw@mail.gmail.com>
 <20240320220008.giyf56mdhxjelwtt@awork3.anarazel.de> <CAApHDvo417naTd+fzZF87XLuC=_ed1567+-5d1v5gAe2VyLD6Q@mail.gmail.com>
 <20240320222057.p7low72xnihz6cn4@awork3.anarazel.de> <CA+hUKGJP1B_rE8-Mef8U-1d9aKdZJfBLBjMpS6ufrRpMb6cr-w@mail.gmail.com>
In-Reply-To: <CA+hUKGJP1B_rE8-Mef8U-1d9aKdZJfBLBjMpS6ufrRpMb6cr-w@mail.gmail.com>
From: Thomas Munro <thomas.munro@gmail.com>
Date: Mon, 10 Feb 2025 16:42:14 +1300
Message-ID: <CA+hUKG+EvNpdhtmAmZp8iAn71QtPk6bCsEwuupFr2MjGg4oOiw@mail.gmail.com>
Subject: Re: Trying to build x86 version on windows using meson
To: Andres Freund <andres@anarazel.de>
Cc: David Rowley <dgrowleyml@gmail.com>, Dave Cramer <davecramer@gmail.com>, 
	PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CA%2BhUKG%2BEvNpdhtmAmZp8iAn71QtPk6bCsEwuupFr2MjGg4oOiw%40mail.gmail.com>
Precedence: bulk

On Mon, Jul 22, 2024 at 12:20=E2=80=AFAM Thomas Munro <thomas.munro@gmail.c=
om> wrote:
> On Thu, Mar 21, 2024 at 11:21=E2=80=AFAM Andres Freund <andres@anarazel.d=
e> wrote:
> > Obviously tests can't run in that environment, but building should be
> > possible. I can e.g. build postgres for x86-64 windows on my linux mach=
ine,
> > but can't run the tests (in theory they could be run with wine, but win=
e isn't
> > complete enough to run postgres).
>
> For anyone interested in that, the most apparent reason why WINE
> currently can't run a cross-build of psql.exe or postgres.exe on a
> Linux/FreeBSD/macOS host is now on their bug list[1] and just needs
> someone to write an easy patch.  I dimly recall there were more subtle
> things that broke here and there before the relevant change of ours
> went in, and it would be pretty cool if we could make a list and
> report 'em...
>
> [1] https://bugs.winehq.org/show_bug.cgi?id=3D56951

Just for the record, apparently they fixed that one.