From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Stefan Sundin via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org
Cc: Stefan Sundin <git@stefansundin.com>
Subject: Re: [PATCH] Makefile: suppress macOS deprecation warning
Date: Sun, 20 Nov 2022 08:48:25 +0700 [thread overview]
Message-ID: <a3cfe081-1e68-edda-b797-e68356988046@gmail.com> (raw)
In-Reply-To: <pull.1422.git.1668888407433.gitgitgadget@gmail.com>
On 11/20/22 03:06, Stefan Sundin via GitGitGadget wrote:
> From: Stefan Sundin <git@stefansundin.com>
>
> Compiling git on macOS 13 emits the following deprecation warning:
>
> CC compat/fsmonitor/fsm-listen-darwin.o
> compat/fsmonitor/fsm-listen-darwin.c:495:2: warning: 'FSEventStreamScheduleWithRunLoop' is deprecated: first deprecated in macOS 13.0 - Use FSEventStreamSetDispatchQueue instead. [-Wdeprecated-declarations]
> FSEventStreamScheduleWithRunLoop(data->stream, data->rl, kCFRunLoopDefaultMode);
> ^
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/CoreServices.framework/Frameworks/FSEvents.framework/Headers/FSEvents.h:1138:1: note: 'FSEventStreamScheduleWithRunLoop' has been explicitly marked deprecated here
> FSEventStreamScheduleWithRunLoop(
> ^
> 1 warning generated.
>
> Setting a minimum macOS version will suppress this deprecation warning.
> Using a version lower than 10.13 will cause other warning messages to
> be emitted.
>
Why don't instead follow the suggestion on the warning message
(FSEventStreamSetDispatchQueue) instead?
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-11-20 1:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 20:06 [PATCH] Makefile: suppress macOS deprecation warning Stefan Sundin via GitGitGadget
2022-11-20 1:48 ` Bagas Sanjaya [this message]
2022-11-20 2:14 ` Stefan Sundin
2022-11-20 12:29 ` Bagas Sanjaya
2022-12-01 18:53 ` Jeff Hostetler
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a3cfe081-1e68-edda-b797-e68356988046@gmail.com \
--to=bagasdotme@gmail.com \
--cc=git@stefansundin.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.