| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | Regina Obe <lr(at)pcorp(dot)us>, '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-14 08:56:37 |
| Message-ID: | 2850891.1615712197@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Heikki Linnakangas <hlinnaka(at)iki(dot)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
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-03-14 17:58:51 | Re: BUG #16920: Can't compile PostGIS with MingW64 against PostgreSQL 14 head |
| Previous Message | Heikki Linnakangas | 2021-03-14 08:10:15 | Re: BUG #16920: Can't compile PostGIS with MingW64 against PostgreSQL 14 head |