| From: | "Regina Obe" <lr(at)pcorp(dot)us> |
|---|---|
| To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | '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-13 04:36:37 |
| Message-ID: | 000e01d717c2$7533c3e0$5f9b4ba0$@pcorp.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> "Regina Obe" <lr(at)pcorp(dot)us> writes:
> >> (FWIW, walleye's owners report that the failure goes away when they
> >> change their compiler options to more debug-friendly settings. Hmm.)
>
> > What is considered a more debug-friendly setting?
>
> Apparently they don't see a crash with CFLAGS="-ggdb -Og -g3"
> (as opposed to the default -O2 possibly with -g).
>
> > As far as crashers go, they all seem to be crashing at the
> > 0x00000000008da31a in pg_re_throw () at elog.c:1776
>
> Cool, thanks for confirming that. At least now we know what it is we
don't
> know.
>
> regards, tom lane
I just tested latest PG13 stable branch with same --configure as I used for
PG14 and all tests pass even with --enable-cassert.
So I guess something changed in master.
I thought maybe there was some overriding of some of the CFLAGS but the
configure.log of both PG13 and PG14 show the same
CFLAGS='-O2 -pipe -fno-ident
-I/c/mingw810/x86_64-810-posix-seh-rt_v6-rev0/mingw64/opt/include
-I/c/mingw810/prerequisites/x86_64-zlib-static/include
-I/c/mingw810/prerequisites/x86_64-w64-mingw32-static/include'
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-03-13 06:10:00 | Re: BUG #16920: Can't compile PostGIS with MingW64 against PostgreSQL 14 head |
| Previous Message | Tom Lane | 2021-03-12 22:57:30 | Re: BUG #16920: Can't compile PostGIS with MingW64 against PostgreSQL 14 head |