pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feed From: Tom Lane <tgl@sss.pgh.pa.us>
To: Regina Obe <lr@pcorp.us>
Cc: 'Heikki Linnakangas' <hlinnaka@iki.fi>
Cc: 'Juan José SantamarÃa Flecha' <juanjo.santamaria@gmail.com>
Cc: 'PostgreSQL mailing lists' <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #16920: Can't compile PostGIS with MingW64 against PostgreSQL 14 head
Date: Mon, 15 Mar 2021 12:12:59 -0400
Message-ID: <3009860.1615824779@sss.pgh.pa.us> (raw )
In-Reply-To: <000501d71932$7da0fa40$78e2eec0$@pcorp.us >
References: <16920-2332590daf58407c@postgresql.org >
<2291040.1615474929@sss.pgh.pa.us >
<000501d71691$c616a200$5243e600$@pcorp.us >
<2294904.1615480631@sss.pgh.pa.us >
<000401d716a0$1ed0fc70$5c72f550$@pcorp.us >
<2309396.1615485820@sss.pgh.pa.us >
<CAC+AXB3_u1LQ7+WPLu2jZN5Y0kdVx10kkSi7XARN4oLSq9-vrQ@mail.gmail.com >
<004301d71772$f3336020$d99a2060$@pcorp.us >
<2551612.1615579995@sss.pgh.pa.us >
<000201d71781$a0c5da20$e2518e60$@pcorp.us >
<2555584.1615585679@sss.pgh.pa.us >
<000201d71792$1a916800$4fb43800$@pcorp.us >
<2558564.1615589850@sss.pgh.pa.us >
<000e01d717c2$7533c3e0$5f9b4ba0$@pcorp.us >
<2589899.1615615800@sss.pgh.pa.us >
<001801d71833$3eb81890$bc2849b0$@pcorp.us >
<2718080.1615661446@sss.pgh.pa.us >
<002d01d7183d$dda66420$98f32c60$@pcorp.us >
<CAC+AXB1N24Av=TyzRp82Jb_ArZQ0LwamfHu-YwsOhYDFfYULdA@mail.gmail.com >
<2730776.1615672184@sss.pgh.pa.us >
<2735801.1615678739@sss.pgh.pa.us >
<000d01d71869$2dabde70$89039b50$@pcorp.us >
<0bf7c953-ea90-7c74-0f97-4e0e83d09dc9@iki.fi >
<2850891.1615712! ! 197@sss.pgh.pa.us >
<2 872301.1615744731@sss.pgh.pa.us >
<000501d71932$7da0fa40$78e2eec0$@pcorp.us >
"Regina Obe" <lr@pcorp.us> writes:
>> I trust none of the buildfarm animals are still using old mingw versions.
> The mingw64 gcc 8.1.0/msys2 I am using granted is not a spring chicken. I
> don't think it's 5 years old, but could be.
According to [1], gcc 8.1 came out a little under 3 years ago, so I guess
it's safe to assume that that package also contains the fix in question.
Meanwhile, walleye's owners have confirmed off-list that the proposed
patch fixes things for them too. I'm going to go ahead and push it
to HEAD, so we can get some further testing. Although I remain worried
about this being an ABI break, I don't think we are locked into it
until we get to beta, or maybe even RC stage.
regards, tom lane
[1] https://www.gnu.org/software/gcc/releases.html
view thread (33+ messages) latest in thread
Message-ID: <3009860.1615824779@sss.pgh.pa.us>
Permalink: ../3009860.1615824779@sss.pgh.pa.us/
Also on: postgresql.org/message-id/3009860.1615824779@sss.pgh.pa.us
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, lr@pcorp.us, hlinnaka@iki.fi, juanjo.santamaria@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16920: Can't compile PostGIS with MingW64 against PostgreSQL 14 head
In-Reply-To: <3009860.1615824779@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox