From: Eli Zaretskii <eliz@gnu.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: alan@idiocy.org, pcr910303@icloud.com, emacs-devel@gnu.org
Subject: Re: macOS/GCC support policy
Date: Fri, 02 Aug 2019 18:05:20 +0300 [thread overview]
Message-ID: <83blx7fw0f.fsf@gnu.org> (raw)
In-Reply-To: <CAArVCkQG_XeG7RCbFwZqNeOvx-gXNBJ9B+pHpbFJFRhpX=dzVQ@mail.gmail.com> (message from Philipp Stephani on Fri, 2 Aug 2019 16:55:02 +0200)
> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Fri, 2 Aug 2019 16:55:02 +0200
> Cc: Alan Third <alan@idiocy.org>, pcr910303@icloud.com,
> Emacs developers <emacs-devel@gnu.org>
>
> /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/objc/NSObject.h:22:4:
> error: unknown type name 'instancetype'
> 22 | - (instancetype)self;
> | ^~~~~~~~~~~~
>
> (lots of similar errors follow)
>
> This indicates that GCC treats the header as C instead of Objective C.
> Which is interesting because -x objective-c is given explicitly. Does
> GCC need some other flag to force compilation as Objective C?
Searching the Internet for this error seems to suggest that this SDK's
header files are supposed to be compiled only by clang, i.e. their GCC
compilation is deliberately broken by Apple.
Why does Emacs need AppKit/AppKit.h? If this is for some important
functionality, and if we cannot find a compatible replacement, I guess
the conclusion is that we cannot build Emacs on macOS with GCC due to
the Apple system headers.
next prev parent reply other threads:[~2019-08-02 15:05 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 19:23 [PATCH v4] Enable xwidgets on macOS Sungbin Jo
2019-07-19 4:16 ` [PATCH v5] " Sungbin Jo
2019-07-19 19:17 ` Alan Third
2019-07-19 19:25 ` Savannah down (was: [PATCH v5] Enable xwidgets on macOS) Paul Eggert
2019-07-20 8:21 ` [PATCH v5] Enable xwidgets on macOS Eli Zaretskii
2019-07-23 18:36 ` 조성빈
2019-07-25 18:51 ` 조성빈
2019-07-26 5:55 ` Eli Zaretskii
2019-07-27 2:48 ` Richard Stallman
2019-07-27 8:38 ` Eli Zaretskii
2019-07-27 10:41 ` Eli Zaretskii
2019-07-27 12:35 ` 조성빈
2019-07-27 13:03 ` Eli Zaretskii
2019-07-29 17:08 ` 조성빈
2019-08-03 10:03 ` Eli Zaretskii
2019-08-03 10:52 ` 조성빈
2019-07-29 20:26 ` Alan Third
2019-07-29 21:02 ` Stefan Monnier
2019-07-30 15:35 ` 조성빈
2019-07-30 19:25 ` Stefan Monnier
2019-07-31 15:52 ` 조성빈
2019-07-30 15:33 ` 조성빈
2019-07-30 19:12 ` Juri Linkov
2019-07-31 15:55 ` 조성빈
2019-07-31 19:56 ` Alan Third
2019-08-01 2:35 ` Eli Zaretskii
2019-08-01 4:00 ` 조성빈
2019-08-02 0:47 ` Richard Stallman
2019-08-02 7:02 ` Eli Zaretskii
2019-08-03 2:23 ` Richard Stallman
2019-08-03 6:58 ` Eli Zaretskii
2019-08-01 21:39 ` macOS/GCC support policy (was: [PATCH v5] Enable xwidgets on macOS) Alan Third
2019-08-02 2:22 ` Noam Postavsky
2019-08-02 6:56 ` macOS/GCC support policy Eli Zaretskii
2019-08-02 10:08 ` Philipp Stephani
2019-08-02 11:51 ` Eli Zaretskii
2019-08-02 14:55 ` Philipp Stephani
2019-08-02 14:59 ` Philipp Stephani
2019-08-02 15:06 ` Philipp Stephani
2019-08-02 15:05 ` Eli Zaretskii [this message]
2019-08-03 11:02 ` Alan Third
2019-08-03 11:10 ` Eli Zaretskii
2019-08-03 11:18 ` Alan Third
2019-08-03 11:43 ` Eli Zaretskii
2019-08-04 2:56 ` Richard Stallman
2019-08-10 9:56 ` 조성빈
2019-08-18 15:43 ` Alan Third
2019-08-18 16:40 ` Eli Zaretskii
2019-08-18 23:42 ` 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=83blx7fw0f.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=alan@idiocy.org \
--cc=emacs-devel@gnu.org \
--cc=p.stephani2@gmail.com \
--cc=pcr910303@icloud.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).