pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feed From: Tom Lane <tgl@sss.pgh.pa.us>
To: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: Regina Obe <lr@pcorp.us>
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 04:56:37 -0400
Message-ID: <2850891.1615712197@sss.pgh.pa.us> (raw )
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 >
<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 >
Heikki Linnakangas <hlinnaka@iki.fi> writes:
> Is this the same issue that was discussed here?
> https://www.postgresql.org/message-id/flat/f1caef93-9640-022e-9211-bbe8755a56b0%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-LsjqRh3Ang7qCSBG0Ga%2B7KwhGqrNUPw%4...
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
view thread (33+ messages) latest in thread
Message-ID: <2850891.1615712197@sss.pgh.pa.us>
Permalink: ../2850891.1615712197@sss.pgh.pa.us/
Also on: postgresql.org/message-id/2850891.1615712197@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, hlinnaka@iki.fi, lr@pcorp.us, 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: <2850891.1615712197@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