Re: fairywren failures

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: fairywren failures
Date: 2019-10-25 19:09:24
Message-ID: 10f2a837-2458-227e-def4-eac250004208@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2019-10-16 13:34, Andrew Dunstan wrote:
>> Could you please check how this animal is labeled? AFAICT, this is not
>> an msys2 build but a mingw build (x86_64-w64-mingw32).
>
> It is indeed an msys2 system. However, when we set MSYSTEM=MINGW64 as
> we do in fairywren's config environment so that the compiler it is
> properly detected by configure (using Msys2's /etc/config.site)
> 'uname -a' reports MINGW64... instead of MSYS...

When you install MSYS2 from msys2.org, you get three possible build
targets, depending on what you set MSYSTEM to:

MSYSTEM=MINGW32
MSYSTEM=MINGW64
MSYSTEM=MSYS

When a buildfarm member identifiers itself as "msys ... 2", then I would
expect the third variant, but that's not what it's doing. A
MSYSTEM=MSYS build is similar to a Cygwin build (since MSYS2 is a fork
of Cygwin), which is also a valid thing to do, but it's obviously quite
different from a mingw build.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2019-10-25 19:32:45 MinGW compiler warnings in ecpg tests
Previous Message Paul Jungwirth 2019-10-25 18:32:05 Re: Add json_object(text[], json[])?