From: Jeff Hostetler <git@jeffhostetler.com>
To: "René Scharfe" <l.s.r@web.de>, "Git List" <git@vger.kernel.org>
Cc: Jeff Hostetler <jeffhost@microsoft.com>,
Kevin Willford <Kevin.Willford@microsoft.com>,
Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: compat/fsmonitor/fsm-listen-darwin warning on macOS Ventura
Date: Tue, 15 Nov 2022 13:48:26 -0500 [thread overview]
Message-ID: <89762517-bde0-4512-797c-f0c75a8f7e76@jeffhostetler.com> (raw)
In-Reply-To: <5dbd5dd1-3a50-c0ce-d06a-227ec0a89bc6@web.de>
On 11/5/22 1:26 PM, René Scharfe wrote:
> Hi all,
>
> on macOS 13.0 Ventura I get the following warning-turned-error when
> compiling the fsmonitor code:
>
>
> compat/fsmonitor/fsm-listen-darwin.c:495:2: error: 'FSEventStreamScheduleWithRunLoop' is deprecated: first deprecated in macOS 13.0 - Use FSEventStreamSetDispatchQueue instead. [-Werror,-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 error generated.
> make: *** [compat/fsmonitor/fsm-listen-darwin.o] Error 1
>
>
> No idea how to use FSEventStreamSetDispatchQueue. I could run tests
> if that helps.
>
> René
>
Thanks for the note. I'll take a look and see if/how much this
changes things.
Jeff
prev parent reply other threads:[~2022-11-15 18:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-05 17:26 compat/fsmonitor/fsm-listen-darwin warning on macOS Ventura René Scharfe
2022-11-08 3:00 ` Taylor Blau
2022-11-15 18:48 ` Jeff Hostetler [this message]
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=89762517-bde0-4512-797c-f0c75a8f7e76@jeffhostetler.com \
--to=git@jeffhostetler.com \
--cc=Kevin.Willford@microsoft.com \
--cc=git@vger.kernel.org \
--cc=jeffhost@microsoft.com \
--cc=johannes.schindelin@gmx.de \
--cc=l.s.r@web.de \
/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://80x24.org/mirrors/git.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).