| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com> |
| Cc: | Regina Obe <lr(at)pcorp(dot)us>, 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-13 21:49:44 |
| Message-ID: | 2730776.1615672184@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
=?UTF-8?Q?Juan_Jos=C3=A9_Santamar=C3=ADa_Flecha?= <juanjo(dot)santamaria(at)gmail(dot)com> 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 the
> 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 <setjmp.h>'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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-03-13 23:38:59 | Re: BUG #16920: Can't compile PostGIS with MingW64 against PostgreSQL 14 head |
| Previous Message | Juan José Santamaría Flecha | 2021-03-13 20:49:12 | Re: BUG #16920: Can't compile PostGIS with MingW64 against PostgreSQL 14 head |