From: Pankaj Jangid <pankaj@codeisgreat.org>
To: emacs-devel@gnu.org
Subject: Re: Getting ready to land native-compilation on master
Date: Wed, 14 Apr 2021 10:09:01 +0530 [thread overview]
Message-ID: <m2o8ehlbtm.fsf@codeisgreat.org> (raw)
In-Reply-To: 83v98v7dzs.fsf@gnu.org
Eli Zaretskii <eliz@gnu.org> writes:
> AFAICT, we are quite ready to land this important feature. The branch
> was tested on several systems and is in good shape: many issues and
> bugs were fixed, and currently no known issues remain that block the
> merge. (There's a lot yet to do wrt documenting the feature and its
> various aspects, but that can be done on master after merging.)
I have started using Emacs from ‘native-comp’ branch last week. I am
doing this for the first time and following instructions from Andrea’s
gccemacs page.
I am on macos and after launching Emacs, I get this libgccjit
error. Is this something that I can ignore for now?
--8<---------------cut here---------------start------------->8---
Warning (comp): libgccjit.so: error: error invoking gcc driver Disable showing Disable logging
Warning (comp): /Users/pankaj/Applications/Emacs.app/Contents/Resources/lisp/emacs-lisp/cl-lib.el.gz: Error: Internal native compiler error failed to compile Disable showing Disable logging
--8<---------------cut here---------------end--------------->8---
Further, there are lots of compiler warnings from different package, as I
use Emacs. That means the native compilation is definitely working.
Other than this I haven’t noticed anything that could be a blocker. My
several packages, Gnus, everything is working fine.
--
Regards
Pankaj Jangid
next prev parent reply other threads:[~2021-04-14 4:39 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 14:02 Getting ready to land native-compilation on master Eli Zaretskii
2021-04-09 14:27 ` tomas
2021-04-09 14:33 ` Stefan Kangas
2021-04-09 14:39 ` T.V Raman
2021-04-09 16:17 ` Pip Cet
2021-04-09 16:35 ` Thierry Volpiatto
2021-04-09 18:57 ` Eli Zaretskii
2021-04-10 5:39 ` Thierry Volpiatto
2021-04-09 17:12 ` Jens C. Jensen
2021-04-09 18:53 ` Stefan Monnier
2021-04-09 18:59 ` Jens C. Jensen
2021-04-09 22:43 ` Stefan Monnier
2021-04-10 8:45 ` Jens C. Jensen
2021-04-10 13:10 ` Stefan Monnier
2021-04-09 19:08 ` Andrea Corallo via Emacs development discussions.
2021-04-09 19:14 ` Eli Zaretskii
2021-04-10 0:07 ` Andy Moreton
2021-04-10 7:23 ` Eli Zaretskii
2021-04-10 11:40 ` Andy Moreton
2021-04-09 18:09 ` Sujith Manoharan
2021-04-09 18:50 ` Eli Zaretskii
2021-04-09 18:27 ` Alex Bennée
2021-04-09 18:48 ` Andrea Corallo via Emacs development discussions.
2021-04-14 4:39 ` Pankaj Jangid [this message]
2021-04-14 6:31 ` Eli Zaretskii
2021-04-14 9:45 ` Philip Kaludercic
2021-04-14 10:14 ` Andrea Corallo via Emacs development discussions.
2021-04-14 10:35 ` Philip Kaludercic
2021-04-14 10:45 ` Eli Zaretskii
2021-04-14 10:49 ` Eli Zaretskii
2021-04-14 12:57 ` Philip Kaludercic
2021-04-14 13:10 ` Eli Zaretskii
2021-04-14 14:00 ` Philip Kaludercic
2021-04-14 14:35 ` Stefan Kangas
2021-04-14 14:42 ` Philip Kaludercic
2021-04-14 14:50 ` Stefan Monnier
2021-04-14 15:02 ` Eli Zaretskii
2021-04-14 14:37 ` Eli Zaretskii
2021-04-14 14:48 ` Dmitry Gutov
2021-04-14 17:10 ` Eli Zaretskii
2021-04-14 10:48 ` Andrea Corallo via Emacs development discussions.
2021-04-14 15:53 ` wilde
2021-04-14 17:02 ` Eli Zaretskii
2021-04-14 17:28 ` Alex Bennée
2021-04-14 17:41 ` Eli Zaretskii
2021-04-15 11:15 ` Alex Bennée
2021-04-14 18:07 ` Andrea Corallo via Emacs development discussions.
2021-04-14 20:23 ` Stefan Kangas
2021-04-14 22:01 ` Andrea Corallo via Emacs development discussions.
2021-04-15 9:25 ` wilde
2021-04-15 11:19 ` wilde
2021-04-15 16:23 ` Andrea Corallo via Emacs development discussions.
2021-04-27 16:25 ` wilde
2021-04-28 3:06 ` Corwin Brust
2021-04-28 17:52 ` Jose E. Marchesi
2021-04-29 8:20 ` Arthur Miller
2021-04-22 10:09 ` wilde
2021-04-22 11:14 ` Eli Zaretskii
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=m2o8ehlbtm.fsf@codeisgreat.org \
--to=pankaj@codeisgreat.org \
--cc=emacs-devel@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).