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 1lLMYQ-0007oU-UJ for pgsql-bugs@arkaria.postgresql.org; Sun, 14 Mar 2021 08:56:54 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lLMYP-0003Kq-Of for pgsql-bugs@arkaria.postgresql.org; Sun, 14 Mar 2021 08:56:53 +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 1lLMYP-0003Kj-IS for pgsql-bugs@lists.postgresql.org; Sun, 14 Mar 2021 08:56:53 +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 1lLMYN-00031n-H9 for pgsql-bugs@lists.postgresql.org; Sun, 14 Mar 2021 08:56:52 +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 12E8ubkR2850892; Sun, 14 Mar 2021 04:56:37 -0400 From: Tom Lane To: Heikki Linnakangas cc: Regina Obe , =?UTF-8?Q?=27Juan_Jos=c3=a9_Santamar=c3=ada_Flecha=27?= , "'PostgreSQL mailing lists'" Subject: Re: BUG #16920: Can't compile PostGIS with MingW64 against PostgreSQL 14 head In-reply-to: <0bf7c953-ea90-7c74-0f97-4e0e83d09dc9@iki.fi> 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> <2730776.1615672184@sss.pgh.pa.us> <2735801.1615678739@sss.pgh.pa.us> <000d01d71869$2dabde70$89039b50$@pcorp.us> <0bf7c953-ea90-7c74-0f97-4e0e83d09dc9@iki.fi> Comments: In-reply-to Heikki Linnakangas message dated "Sun, 14 Mar 2021 10:10:15 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2850890.1615712197.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Sun, 14 Mar 2021 04:56:37 -0400 Message-ID: <2850891.1615712197@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Heikki Linnakangas writes: > Is this the same issue that was discussed here? > https://www.postgresql.org/message-id/flat/f1caef93-9640-022e-9211-bbe87= 55a56b0%402ndQuadrant.com Hard to tell. We've seen reports like this come and go for no apparent reason -- for example, if you check the previous thread at https://www.postgresql.org/message-id/flat/CA%2BBEBhvHhM-Bn628pf-LsjqRh3An= g7qCSBG0Ga%2B7KwhGqrNUPw%40mail.gmail.com the problem appeared to bisect down to commits that logically should have nothing to do with it. Which is just like the current situation. That smells like a compiler bug to me. So the idea that "this setjmp implementation is just broken" is gaining some credence in my eyes. Googling "mingw setjmp" shows that similar complaints have been around for a decade ... which is weird, you'd think they'd have fixed it by now. regards, tom lane