Re: fairywren failures - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: fairywren failures
Date
Msg-id 10f2a837-2458-227e-def4-eac250004208@2ndquadrant.com
Whole thread Raw
In response to Re: fairywren failures  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
Responses Re: fairywren failures  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
List 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



pgsql-hackers by date:

Previous
From: Paul Jungwirth
Date:
Subject: Re: Add json_object(text[], json[])?
Next
From: Peter Eisentraut
Date:
Subject: MinGW compiler warnings in ecpg tests