Re: BUG #16920: Can't compile PostGIS with MingW64 against PostgreSQL 14 head

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Regina Obe" <lr(at)pcorp(dot)us>
Cc: "'Heikki Linnakangas'" <hlinnaka(at)iki(dot)fi>, 'Juan José Santamaría Flecha' <juanjo(dot)santamaria(at)gmail(dot)com>, "'PostgreSQL mailing lists'" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #16920: Can't compile PostGIS with MingW64 against PostgreSQL 14 head
Date: 2021-03-15 16:12:59
Message-ID: 3009860.1615824779@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Regina Obe" <lr(at)pcorp(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Eirik Bakke 2021-03-15 17:14:06 RE: BUG #16926: initdb fails on Windows when binary path contains certain non-ASCII characters
Previous Message Tom Lane 2021-03-15 16:06:16 Re: BUG #16926: initdb fails on Windows when binary path contains certain non-ASCII characters