From: Jacob Faibussowitsch <jacob.fai@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: "Gerd Möllmann" <gerd.moellmann@gmail.com>, 58966@debbugs.gnu.org
Subject: bug#58966: [Trunk] Xcode 14.1+ (and macOS 13.0+) deprecate sprintf()
Date: Fri, 4 Nov 2022 17:07:09 -0400 [thread overview]
Message-ID: <0DFAD726-8BD3-4A05-B0DA-E5C3578B55EB@gmail.com> (raw)
In-Reply-To: <91d5853d-b810-3b69-93cf-772c81c34f7e@cs.ucla.edu>
Sorry for the delay. I just tested most recent master (most recent commit summary below):
commit 44ad42240069d8d82772b0c0ef5ec93c2566ca7e (HEAD -> master, origin/master, origin/HEAD)
Author: Stefan Kangas <stefankangas@gmail.com>
Date: Fri Nov 4 20:26:01 2022 +0100
And I don’t see any warnings anymore -- I am assuming your commit made it in. Thanks for the fix.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Nov 3, 2022, at 14:30, Paul Eggert <eggert@cs.ucla.edu> wrote:
>
> It appears that Apple has gone on the warpath against sprintf even if you compile with plain 'gcc' with no options, which means --disable-gcc-warnings does not suppress the false alarms.
>
> I installed the attached further patch to attempt to pacify Apple's compiler; please give it a try.
>
> Perhaps Apple's compiler will start complaining about strcpy next....
> <0001-Improve-suppression-of-bogus-macOS-warnings.patch>
next prev parent reply other threads:[~2022-11-04 21:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 13:56 bug#58966: [Trunk] Xcode 14.1+ (and macOS 13.0+) deprecate sprintf() Jacob Faibussowitsch
2022-11-03 5:56 ` Gerd Möllmann
2022-11-03 8:16 ` Eli Zaretskii
2022-11-03 9:00 ` Gerd Möllmann
2022-11-03 9:15 ` Eli Zaretskii
2022-11-03 9:36 ` Gerd Möllmann
2022-11-03 14:40 ` Jacob Faibussowitsch
2022-11-03 14:43 ` Gerd Möllmann
2022-11-03 14:48 ` Jacob Faibussowitsch
2022-11-03 15:22 ` Gerd Möllmann
2022-11-03 15:30 ` Jacob Faibussowitsch
2022-11-03 16:15 ` Gerd Möllmann
2022-11-03 16:19 ` Gerd Möllmann
2022-11-03 18:30 ` Paul Eggert
2022-11-04 21:07 ` Jacob Faibussowitsch [this message]
2022-11-05 3:12 ` Richard Stallman
2022-11-05 16:26 ` Stefan Kangas
2022-11-05 20:00 ` Paul Eggert
2022-11-07 7:46 ` Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0DFAD726-8BD3-4A05-B0DA-E5C3578B55EB@gmail.com \
--to=jacob.fai@gmail.com \
--cc=58966@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=gerd.moellmann@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).