pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Regina Obe <lr@pcorp.us>
To: 'Tom Lane' <tgl@sss.pgh.pa.us>
To: '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: Sun, 14 Mar 2021 20:31:06 -0400
Message-ID: <000501d71932$7da0fa40$78e2eec0$@pcorp.us> (raw)
In-Reply-To: <2872301.1615744731@sss.pgh.pa.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>

> I came across a very relevant mingw bug report:
> 
> https://sourceforge.net/p/mingw-w64/bugs/465/
> 
> in which they were trying to clear an 8-byte jmp_buf field with a 4-byte
> instruction.  That would go a long way towards explaining the sort of
> problems we're seeing ... except it was fixed five years ago.
> I trust none of the buildfarm animals are still using old mingw versions.
> 
> 			regards, tom lane

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.

That said I did download the latest mingw64/msys2 package:

gcc.exe (Rev6, Built by MSYS2 project) 10.2.0

and I encountered the same crashers using the same configure when compiling.

Maybe it has more to do with the MSVCRT which mingw just uses what is on the
system - C:\WINDOWS\System32\msvcrt.dll
I'm running windows 10 which should have a fairly recent MSVCRT.  I wonder
if things would be different on windows 2019.


Thanks,
Regina








view thread (33+ messages)  latest in thread

Message-ID: <000501d71932$7da0fa40$78e2eec0$@pcorp.us>
Permalink:  ../000501d71932$7da0fa40$78e2eec0$@pcorp.us/
Also on:    postgresql.org/message-id/000501d71932$7da0fa40$78e2eec0$@pcorp.us

 · 

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: lr@pcorp.us, tgl@sss.pgh.pa.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: <000501d71932$7da0fa40$78e2eec0$@pcorp.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