From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: arne_bab@web.de, emacs-devel@gnu.org
Subject: Re: [ELPA] New package xeft.el
Date: Tue, 17 Jan 2023 13:53:30 +0200 [thread overview]
Message-ID: <8335894bt1.fsf@gnu.org> (raw)
In-Reply-To: <E1pHe2o-0003iu-O6@fencepost.gnu.org> (message from Richard Stallman on Mon, 16 Jan 2023 23:57:58 -0500)
> From: Richard Stallman <rms@gnu.org>
> Cc: emacs-devel@gnu.org
> Date: Mon, 16 Jan 2023 23:57:58 -0500
>
> > Usually a package is either native-compiled on first usage or directly
> > on installation.
>
> Are you sure? Nothing gets native-compiled automatically for me,
> and that's the way I want it. I don't use native compilation.
What does the below produce in your Emacs?
M-: (string-match-p "NATIVE_COMP" system-configuration-features) RET
If it produces nil, it means your build doesn't have
native-compilation available, which is why you don't see Lisp packages
native-compiled when loaded for the first time (a.k.a. "JIT").
> Is it possible that you're talking about behavior that you have
> specifically enabled, and does not happen by default?
The build needs to be with native-compilation, and then it is
automatic. Usually, just installing libgccjit (part of the GCC suite,
perhaps an optional part) and rebuilding Emacs is enough, assuming you
have GCC and Binutils.
next prev parent reply other threads:[~2023-01-17 11:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 4:11 [ELPA] New package xeft.el Yuan Fu
2023-01-04 8:08 ` Jean Louis
2023-01-04 16:46 ` Fu Yuan
2023-01-06 17:34 ` Jean Louis
2023-01-10 10:48 ` Yuan Fu
2023-01-04 19:24 ` Stefan Monnier
2023-01-04 19:38 ` Karl Fogel
2023-01-06 5:48 ` Yuan Fu
2023-01-06 5:46 ` Yuan Fu
2023-01-06 16:21 ` Stefan Monnier
2023-01-10 10:57 ` Yuan Fu
2023-01-13 4:51 ` Richard Stallman
2023-01-13 9:54 ` Dr. Arne Babenhauserheide
2023-01-15 5:14 ` Richard Stallman
2023-01-16 7:48 ` Dr. Arne Babenhauserheide
2023-01-17 4:57 ` Richard Stallman
2023-01-17 11:53 ` Eli Zaretskii [this message]
2023-01-23 4:23 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8335894bt1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=arne_bab@web.de \
--cc=emacs-devel@gnu.org \
--cc=rms@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.