From: Stephen Berman <stephen.berman@gmx.net>
To: Konrad Podczeck <konrad.podczeck@univie.ac.at>
Cc: 48344@debbugs.gnu.org
Subject: bug#48344: Problem with native-compilation
Date: Tue, 11 May 2021 13:21:39 +0200 [thread overview]
Message-ID: <87o8dh7by4.fsf@rub.de> (raw)
In-Reply-To: <23D430C9-DF63-45DE-9FD2-1DFB8BDA15BF@univie.ac.at> (Konrad Podczeck's message of "Tue, 11 May 2021 13:11:10 +0200")
On Tue, 11 May 2021 13:11:10 +0200 Konrad Podczeck <konrad.podczeck@univie.ac.at> wrote:
> I installed libgccjit from homebrew on the latest MacOS.
>
> Using the option --with-native-compilation to build Emacs, during the configure phase I got:
>
> checking libgccjit.h usability... yes
> checking libgccjit.h presence... yes
> checking for libgccjit.h... yes
> configure: error: Installed libgccjit has failed passing the smoke test.
>
> “usabilty” yes, but then “failed” some test, look contradictory.
> What is the “smoke test”?
https://en.wikipedia.org/wiki/Smoke_testing_%28software%29
> There is no hint in any of the docs coming with Emacs.
The complete error message in the configure file is this:
"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>."
(I haven't yet tried building --with-native-compilation so I don't know
if the configure output shows the complete message.)
Steve Berman
next prev parent reply other threads:[~2021-05-11 11:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 11:11 bug#48344: Problem with native-compilation Konrad Podczeck
2021-05-11 11:21 ` Stephen Berman [this message]
2021-05-11 19:21 ` Konrad Podczeck
2021-05-12 12:58 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87o8dh7by4.fsf@rub.de \
--to=stephen.berman@gmx.net \
--cc=48344@debbugs.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).