[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ELPA] New package xeft.el
From: |
Eli Zaretskii |
Subject: |
Re: [ELPA] New package xeft.el |
Date: |
Tue, 17 Jan 2023 13:53:30 +0200 |
> 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.
- Re: [ELPA] New package xeft.el, (continued)
- Re: [ELPA] New package xeft.el, Karl Fogel, 2023/01/04
- Re: [ELPA] New package xeft.el, Yuan Fu, 2023/01/06
- Re: [ELPA] New package xeft.el, Stefan Monnier, 2023/01/06
- Re: [ELPA] New package xeft.el, Yuan Fu, 2023/01/10
- Re: [ELPA] New package xeft.el, Richard Stallman, 2023/01/12
- Re: [ELPA] New package xeft.el, Dr. Arne Babenhauserheide, 2023/01/13
- Re: [ELPA] New package xeft.el, Richard Stallman, 2023/01/15
- Re: [ELPA] New package xeft.el, Dr. Arne Babenhauserheide, 2023/01/16
- Re: [ELPA] New package xeft.el, Richard Stallman, 2023/01/16
- Re: [ELPA] New package xeft.el,
Eli Zaretskii <=
- Re: [ELPA] New package xeft.el, Richard Stallman, 2023/01/22