unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Niels Søndergaard" <nisoni@algon.dk>
To: Konrad Podczeck <konrad.podczeck@univie.ac.at>
Cc: "Niels Søndergaard" <nisoni@algon.dk>,
	"Alan Third" <alan@idiocy.org>,
	48804@debbugs.gnu.org
Subject: bug#48804: 27.2; compilation emacs on macOS
Date: Fri, 4 Jun 2021 14:19:54 +0200	[thread overview]
Message-ID: <BEF6760F-C190-454A-9728-E28E642A6F3E@algon.dk> (raw)
In-Reply-To: <DD6FE42F-2516-40A2-9189-4B9696B705A0@univie.ac.at>

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

Thanks,
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 ….. 

but thanks

mvh
Niels 

> Den 4. jun. 2021 kl. 13.52 skrev Konrad Podczeck <konrad.podczeck@univie.ac.at>:
> 
> 
> 
>> Am 04.06.2021 um 08:00 schrieb Eli Zaretskii <eliz@gnu.org <mailto:eliz@gnu.org>>:
>> 
>>> Date: Thu, 3 Jun 2021 22:34:44 +0100
>>> From: Alan Third <alan@idiocy.org <mailto:alan@idiocy.org>>
>>> Cc: nisoni@algon.dk <mailto:nisoni@algon.dk>, 48804@debbugs.gnu.org <mailto:48804@debbugs.gnu.org>
>>> 
>>>> in addition to libgccjit, you need to install gcc-11, and to insert somethin like the following into your .bash_profile
>>>> 
>>>> export CC="/usr/local/Cellar/gcc/11.1.0/bin/gcc-11”
>>>> 
>>>> (assuming you use homebrew to install additional unix tools).
>>> 
>>> FYI GCC is unable to build GUI emacs on macOS (or at least the native
>>> GUI). And there's no requirement to build Emacs with GCC for native
>>> compilation to work, as long as libgccjit was installed with Homebrew,
>>> Emacs configure should be able to find it.
>> 
>> That is true, but AFAIK libgccjit invokes gcc as part of the native
>> compilation, so GCC does need to be installed, even if Emacs is built
>> with another compiler.
> 
> 
> For this reason, I mailed to the homebrew people, and got this response:
> 
> "What compiler are you using? Do you have Homebrew gcc installed?"
> 
> After installing gcc-11 from homebrew, and inserting the line
> 
> export CC="/usr/local/Cellar/gcc/11.1.0/bin/gcc-11”
> 
> in my .bash_profile, the “smoke test" error message (about which this disussion started) was gone and I could build Emacs with the native compile option.
>> 
>> (And maybe we should ping the GCC developers to finish the work on the
>> features needed to build Emacs -- there's a Bugzilla PR, where, last
>> time I checked, there was some work being done).
> 


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

  reply	other threads:[~2021-06-04 12:19 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 [this message]
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
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=BEF6760F-C190-454A-9728-E28E642A6F3E@algon.dk \
    --to=nisoni@algon.dk \
    --cc=48804@debbugs.gnu.org \
    --cc=alan@idiocy.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).