From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: macos ventura SDK spews warnings |
Date: | 2022-10-16 05:34:43 |
Message-ID: | 20221016053443.f6oyf7znbrfm4m4w@awork3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 2022-10-15 21:00:00 -0400, Tom Lane wrote:
> I wrote:
> > snprintf is required by POSIX going back to SUSv2, so it's pretty darn
> > hard to imagine any currently-used platform that hasn't got it. Even
> > my now-extinct dinosaur gaur had it (per digging in backup files).
> > I think we could certainly assume its presence in the branches that
> > require C99.
>
> After further thought, I think the best compromise is just that:
>
> (1) apply s/sprintf/snprintf/ patch in branches back to v12, where
> we began to require C99.
>
> (2) in v11 and back to 9.2, enable -Wno-deprecated if available.
>
> One thing motivating this choice is that we're just a couple
> weeks away from the final release of v10. So I'm hesitant to do
> anything that might turn out to be moving the portability goalposts
> in v10. But we're already assuming we can detect -Wno-foo options
> correctly in v10 and older (e.g. 4c5a29c0e), so point (2) seems
> pretty low-risk.
Makes sense to me.
- Andres
From | Date | Subject | |
---|---|---|---|
Next Message | Bharath Rupireddy | 2022-10-16 07:02:56 | Re: Improve description of XLOG_RUNNING_XACTS |
Previous Message | Andres Freund | 2022-10-16 05:25:22 | Re: Use -fvisibility=hidden for shared libraries |