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: "Niels Søndergaard" <nisoni@algon.dk>, 48804@debbugs.gnu.org
Subject: bug#48804: 27.2; compilation emacs on macOS
Date: Thu, 3 Jun 2021 08:51:06 +0200	[thread overview]
Message-ID: <3DE8BABE-F3C7-4A12-A34E-622F6C5A3366@algon.dk> (raw)
In-Reply-To: <8335tzxx6h.fsf@gnu.org>

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

The configure sends a link, but I can’t find the source to compile out of that, neither can I understand, what the “smoke” test is.
I tried to follow the instruktions, but god lost underway….

mvh
Niels


> Den 3. jun. 2021 kl. 08.46 skrev Eli Zaretskii <eliz@gnu.org>:
> 
>> From: Niels Søndergaard <nisoni@algon.dk>
>> Date: Thu, 3 Jun 2021 07:54:44 +0200
>> 
>> When trying to compile (28.0.50) with --with-native-compilation, the
>> ./configure comes out with libgccjit failed the smoke test, and the
>> explanation for getting libgccjit is not easy, actual it's very
>> complicated.
> 
> The message is:
> 
>  Installed libgccjit has failed passing the smoke test.
>  You can verify it yourself compiling:
>  <https://gcc.gnu.org/onlinedocs/jit/intro/tutorial01.html>.
>  Please report the issue to your distribution if libgccjit was installed
>  through that.
>  Here instructions on how to compile and install libgccjit from source:
>  <https://gcc.gnu.org/wiki/JIT>
> 
> Could you please be more specific about what is unclear or complicated
> in this message, and how would you like us to make it more clear and
> easy to understand?


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

  reply	other threads:[~2021-06-03  6:51 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 [this message]
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
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=3DE8BABE-F3C7-4A12-A34E-622F6C5A3366@algon.dk \
    --to=nisoni@algon.dk \
    --cc=48804@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).