Re: Cannot find a working 64-bit integer type on Illumos - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Cannot find a working 64-bit integer type on Illumos
Date
Msg-id CA+hUKG+CPwNux6PmQfkhLsGKxEJOLHz_R4J+8GcB2VAWuyDH7Q@mail.gmail.com
Whole thread Raw
In response to Re: Cannot find a working 64-bit integer type on Illumos  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, Dec 5, 2024 at 4:29 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Thomas Munro <thomas.munro@gmail.com> writes:
> > Ahh, correction, it does define it (or else perl would have
> > complained), but it seems that meson magically puts it into the
> > compiler command line without being asked.  So it is defined without
> > pg_config.h being involved, and thus earlier.  Huh.
>
> That does not seem great.  Compile an extension without the same
> CPPFLAGS, you silently get an ABI-incompatible module.  We really
> ought to be putting these ABI-critical flags into pg_config.h.
> It's especially bad that this works differently between autoconf
> and meson builds.

It makes the whole MinGW circus worse that I'd realised:


https://www.postgresql.org/message-id/flat/CA%2BhUKG%2B6ZPD_X5ADMwX2uUtXqe_wv8%2BKQ5xFeAR2zbcodjNZvw%40mail.gmail.com#ddad894fcfa9733d30a579f7eb52ebf6



pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: Windows pg_basebackup unable to create >2GB pg_wal.tar tarballs ("could not close file: Invalid argument" when creating pg_wal.tar of size ~ 2^31 bytes)
Next
From: jian he
Date:
Subject: Re: NOT ENFORCED constraint feature