Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lLC8s-00081P-V5 for pgsql-bugs@arkaria.postgresql.org; Sat, 13 Mar 2021 21:49:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lLC8r-0008Tu-RN for pgsql-bugs@arkaria.postgresql.org; Sat, 13 Mar 2021 21:49:49 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lLC8r-0008RK-L7 for pgsql-bugs@lists.postgresql.org; Sat, 13 Mar 2021 21:49:49 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lLC8p-0006Rp-5x for pgsql-bugs@lists.postgresql.org; Sat, 13 Mar 2021 21:49:48 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 12DLnius2730777; Sat, 13 Mar 2021 16:49:44 -0500 From: Tom Lane To: =?UTF-8?Q?Juan_Jos=C3=A9_Santamar=C3=ADa_Flecha?= cc: Regina Obe , PostgreSQL mailing lists Subject: Re: BUG #16920: Can't compile PostGIS with MingW64 against PostgreSQL 14 head In-reply-to: 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> <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> Comments: In-reply-to =?UTF-8?Q?Juan_Jos=C3=A9_Santamar=C3=ADa_Flecha?= message dated "Sat, 13 Mar 2021 21:49:12 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2730775.1615672184.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Sat, 13 Mar 2021 16:49:44 -0500 Message-ID: <2730776.1615672184@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk =3D?UTF-8?Q?Juan_Jos=3DC3=3DA9_Santamar=3DC3=3DADa_Flecha?=3D writes: > After tweaking my configure a bit I am able to reproduce the problem. I > think the problem is on MinGW-w64's longjmp. The attached patch fixes th= e > issue for me. Hmm, interesting. The gcc manual is quite negative about these though: https://gcc.gnu.org/onlinedocs/gcc/Nonlocal-Gotos.html Also it's not clear that these are compatible with 's version of jmp_buf. What I'm wondering about, looking at that bit of code, is whether the entire premise is correct for MinGW-64. Maybe it does provide real sigsetjmp and we shouldn't be overriding those names? (None of this quite explains why a problem suddenly materialized with 3174d69fb9, though. That did not touch anything near our setjmp/longjmp code AFAICS.) regards, tom lane