From: Filipp Gunbin <fgunbin@fastmail.fm>
To: Jacob Faibussowitsch <jacob.fai@gmail.com>
Cc: 51925@debbugs.gnu.org
Subject: bug#51925: [Trunk][macOS] "vfork" is deprecated
Date: Thu, 18 Nov 2021 20:09:19 +0300 [thread overview]
Message-ID: <m2k0h5xuf4.fsf@fastmail.fm> (raw)
In-Reply-To: <038C2656-DD80-4326-8ED4-4C88F8D69C4A@gmail.com> (Jacob Faibussowitsch's message of "Thu, 18 Nov 2021 09:50:27 -0600")
On 18/11/2021 09:50 -0600, Jacob Faibussowitsch wrote:
> I have had these installed for ages, but as it turns out my Xcode path
> was still pointing to /Applications/Xcode.app/Contents/Developer -_-.
CLT are enough for a working toolchain (XCode itself is not necessary).
I was talking about ensuring "proper" installation just in case
something's wrong with CLT (for example, who knows what macOS update is
doing?). But good that you found the reason.
> Switching to CLT I now don’t get warnings about vfork() when building emacs anymore, but have now gotten the following warning:
>
> nproc.c:321:21: warning: passing 'const int [2]' to parameter of type 'int *' discards qualifiers [-Wincompatible-pointer-types-discards-qualifiers]
> if (sysctl (mib[i], ARRAY_SIZE (mib[i]), &nprocs, &len, NULL, 0) == 0
> ^~~~~~
> /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/sysctl.h:770:21: note: passing argument to parameter here
> int sysctl(int *, u_int, void *, size_t *, void *, size_t);
> ^
I have them too, someone has to fix it.
Filipp
next prev parent reply other threads:[~2021-11-18 17:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 17:50 bug#51925: [Trunk][macOS] "vfork" is deprecated Jacob Faibussowitsch
2021-11-17 17:58 ` Eli Zaretskii
2021-11-17 18:02 ` Jacob Faibussowitsch
2021-11-17 18:08 ` Jacob Faibussowitsch
2021-11-17 18:25 ` Eli Zaretskii
[not found] ` <m2ilwqfuiy.fsf@fastmail.fm>
[not found] ` <D05C8617-3056-4753-A5CE-B0AC8D1FC215@gmail.com>
2021-11-17 20:16 ` Filipp Gunbin
2021-11-18 15:50 ` Jacob Faibussowitsch
2021-11-18 17:09 ` Filipp Gunbin [this message]
2022-09-20 15:20 ` Lars Ingebrigtsen
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=m2k0h5xuf4.fsf@fastmail.fm \
--to=fgunbin@fastmail.fm \
--cc=51925@debbugs.gnu.org \
--cc=jacob.fai@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.