From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Fix C23 compiler warning |
Date: | 2024-10-26 14:16:27 |
Message-ID: | 202410261416.6dn5sgkvwie4@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2024-Oct-25, Tom Lane wrote:
> As I recall, we looked at adopting it some years ago and decided it
> was too much churn for the value (seeing that the long-term plan is
> to go to meson only). Maybe C23 is a reason to rethink, but from
> what I recall of that, it won't be a painless update.
Ah, yeah. That was 2.71 actually:
https://postgr.es/m/3838336.1657985206@sss.pgh.pa.us
1.72 seems to have been released with some fixes from that one. Per
that thread, the related problem you noticed was with m4, and apparently
it was because macOS ships a version from 2006 (1.4.7). Here on Debian
bookworm I have m4 1.4.19; maybe macOS has updated its copy now?
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
From | Date | Subject | |
---|---|---|---|
Next Message | jian he | 2024-10-26 15:12:37 | make all ereport in gram.y print out relative location |
Previous Message | Alvaro Herrera | 2024-10-26 14:14:25 | Re: Enhancing Memory Context Statistics Reporting |