unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Niels Søndergaard" <nisoni@algon.dk>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Alan Third" <alan@idiocy.org>,
	"Niels Søndergaard" <nisoni@algon.dk>,
	"Konrad Podczeck" <konrad.podczeck@univie.ac.at>,
	48804@debbugs.gnu.org
Subject: bug#48804: 27.2; compilation emacs on macOS
Date: Fri, 4 Jun 2021 14:59:54 +0200	[thread overview]
Message-ID: <66405D8B-FDF5-4CCC-BDBF-C54A66BDCD3B@algon.dk> (raw)
In-Reply-To: <8335txn73m.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1950 bytes --]

hello 

Now I god this error in the “configure —with-native-compilation” ,

checking AppKit/AppKit.h usability... no
checking AppKit/AppKit.h presence... yes
configure: WARNING: AppKit/AppKit.h: present but cannot be compiled
configure: WARNING: AppKit/AppKit.h:     check for missing prerequisite headers?
configure: WARNING: AppKit/AppKit.h: see the Autoconf documentation
configure: WARNING: AppKit/AppKit.h:     section "Present But Cannot Be Compiled"
configure: WARNING: AppKit/AppKit.h: proceeding with the compiler's result
configure: WARNING:     ## ------------------------------------ ##
configure: WARNING:     ## Report this to bug-gnu-emacs@gnu.org ##
configure: WARNING:     ## ------------------------------------ ##
checking for AppKit/AppKit.h... no
configure: error: The include files (AppKit/AppKit.h etc) that
are required for a Nextstep build are missing or cannot be compiled.
Either fix this, or re-configure with the option '--without-ns’. 

And I didn’t specify “—with-ns” this time

mvh
Niels
 
> Den 4. jun. 2021 kl. 14.32 skrev Eli Zaretskii <eliz@gnu.org>:
> 
>> Date: Fri, 04 Jun 2021 13:26:38 +0100
>> CC: konrad.podczeck@univie.ac.at,nisoni@algon.dk,48804@debbugs.gnu.org
>> From: Alan Third <alan@idiocy.org>
>> 
>>>> I’ve gcc 10.2.0_4 installed by Homebrew on my new iMac 24” (with M1),
>>> and can’t get a newer version, so I’ll
>>>> properly have to wait ….. 
>>> 
>>> What's wrong with GCC 10?  AFAIK, even GCC 7 comes with libgccjit that
>>> is good enough for Emacs.
>> 
>> I believe that libgccjit only just added support for M1 processors in the last week or two, and for whatever reason the Intel emulation on the Macs doesn't work with the older libgccjit either.
> 
> Should we mention this in NEWS, where we announce native-compilation
> support?  Knowing the prerequisites is important to avoid false
> expectations and frustration.


[-- Attachment #2: Type: text/html, Size: 6509 bytes --]

  parent reply	other threads:[~2021-06-04 12:59 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03  5:54 bug#48804: 27.2; compilation emacs on macOS Niels Søndergaard
2021-06-03  6:46 ` Eli Zaretskii
2021-06-03  6:51   ` Niels Søndergaard
2021-06-03  7:49     ` Eli Zaretskii
2021-06-03  8:12       ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-06-03  9:10         ` Niels Søndergaard
2021-06-03  9:21           ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-06-03  7:57     ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-06-03  8:22 ` Konrad Podczeck
2021-06-03 21:34   ` Alan Third
2021-06-04  6:00     ` Eli Zaretskii
2021-06-04 11:52       ` Konrad Podczeck
2021-06-04 12:19         ` Niels Søndergaard
2021-06-04 12:23           ` Eli Zaretskii
2021-06-04 12:26             ` Alan Third
2021-06-04 12:32               ` Eli Zaretskii
2021-06-04 12:59                 ` Alan Third
2021-06-04 13:03                   ` Niels Søndergaard
2021-06-04 12:59                 ` Niels Søndergaard [this message]
2021-06-04 13:56                   ` Eli Zaretskii
2021-06-04 14:08                     ` Niels Søndergaard
2021-06-04 14:15                       ` Eli Zaretskii
2021-06-04 14:43                         ` Alan Third
2021-06-04 15:02                           ` Niels Søndergaard
2021-06-04 15:15                             ` Niels Søndergaard
2021-06-04 18:55                               ` Eli Zaretskii
2021-06-04 16:04                           ` Doug Davis
2021-06-04 14:33             ` Konrad Podczeck

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=66405D8B-FDF5-4CCC-BDBF-C54A66BDCD3B@algon.dk \
    --to=nisoni@algon.dk \
    --cc=48804@debbugs.gnu.org \
    --cc=alan@idiocy.org \
    --cc=eliz@gnu.org \
    --cc=konrad.podczeck@univie.ac.at \
    /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).