From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
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, 03 Jun 2021 08:12:41 +0000 [thread overview]
Message-ID: <xjfsg1zicxy.fsf@sdf.org> (raw)
In-Reply-To: <83y2brwfou.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 03 Jun 2021 10:49:37 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Niels Søndergaard <nisoni@algon.dk>
>> Date: Thu, 3 Jun 2021 08:51:06 +0200
>> Cc: Niels Søndergaard <nisoni@algon.dk>,
>> 48804@debbugs.gnu.org
>>
>> 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.
>
> The link shows a source of a C program whose first line says:
>
> Smoketest example for libgccjit.so
>
>> I tried to follow the instruktions, but god lost underway….
>
> You mean, the instructions on the URL how to compile the test program?
> They are quite simple: 2 shell commands.
>
> Anyway, I've modified that error message to say this instead:
>
> The installed libgccjit failed to compile and run a test program using
> the libgccjit library; see config.log for the details of the failure.
> The test program can be found here:
> <https://gcc.gnu.org/onlinedocs/jit/intro/tutorial01.html>.
Just a small note, the smoke test we run from the configure is not
exactly the one of the link as we just compile a function returning an
integer. Needless to say that most certainly if one works the other
will too.
Andrea
next prev parent reply other threads:[~2021-06-03 8:12 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 [this message]
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=xjfsg1zicxy.fsf@sdf.org \
--to=bug-gnu-emacs@gnu.org \
--cc=48804@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=eliz@gnu.org \
--cc=nisoni@algon.dk \
/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).