From: Robert Pluim <rpluim@gmail.com>
To: Pankaj Jangid <p4j@j4d.net>
Cc: 39003@debbugs.gnu.org
Subject: bug#39003: 27.0.60; MacOS build fails; probably after pthread_setname_np change
Date: Tue, 07 Jan 2020 09:24:43 +0100 [thread overview]
Message-ID: <m236crad2s.fsf@gmail.com> (raw)
In-Reply-To: <0100016f7ed0e2a4-608aa540-e4fb-41d6-aea2-f931f71f34a3-000000@email.amazonses.com> (Pankaj Jangid's message of "Tue, 7 Jan 2020 07:03:36 +0000")
>>>>> On Tue, 7 Jan 2020 07:03:36 +0000, Pankaj Jangid <p4j@j4d.net> said:
Pankaj> Building on emacs-27. I am getting this error
Pankaj> ```
Pankaj> CC thread.o
Pankaj> CC systhread.o
Pankaj> systhread.c:236:44: error: too many arguments to function call, expected 1, have
Pankaj> 2
Pankaj> pthread_setname_np (*thread_ptr, p_name);
Pankaj> ~~~~~~~~~~~~~~~~~~ ^~~~~~
Pankaj> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/pthread.h:512:1: note:
Pankaj> 'pthread_setname_np' declared here
Pankaj> __API_AVAILABLE(macos(10.6), ios(3.2))
Pankaj> ^
Pankaj> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/Availability.h:496:162: note:
Pankaj> expanded from macro '__API_AVAILABLE'
Pankaj> ...__API_AVAILABLE5, __API_AVAILABLE4, __API_AVAILABLE3, __API_AVAILABLE2, ...
Pankaj> ^
Pankaj> 1 error generated.
Pankaj> make[2]: *** [systhread.o] Error 1
Pankaj> make[1]: *** [src] Error 2
Pankaj> make: *** [bootstrap] Error 2
Pankaj> ```
Pankaj> This is probably due to commit 9063124b9125ed5e2ad87bbb8bd6224526723a92.
Yes. Mattias Engdegård has a patch in process under Bug#38632
Robert
next prev parent reply other threads:[~2020-01-07 8:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 7:03 bug#39003: 27.0.60; MacOS build fails; probably after pthread_setname_np change Pankaj Jangid
2020-01-07 8:24 ` Robert Pluim [this message]
2020-01-07 9:17 ` Pankaj Jangid
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=m236crad2s.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=39003@debbugs.gnu.org \
--cc=p4j@j4d.net \
/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.