all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
* Native compilation
@ 2021-12-22 14:41 dxlcstar
  2021-12-22 16:01 ` Óscar Fuentes
  0 siblings, 1 reply; 3+ messages in thread
From: dxlcstar @ 2021-12-22 14:41 UTC (permalink / raw)
  To: help-gnu-emacs@gnu.org

Hi,

I hope this is not an extremely dumb question.

After installing emacs (mater branch) with native compilation enabled, running
it for the first time invokes deferred compilation for the packages
that I call and use, and eln-cache is populated.

But, subsequent invocations of emacs doesn't seem to start deferred
compilation at all for lisp packages that I didn't use the first time.

I think I am missing something very basic - any suggestions ?

- DX




^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Native compilation
  2021-12-22 14:41 Native compilation dxlcstar
@ 2021-12-22 16:01 ` Óscar Fuentes
  2021-12-23 22:48   ` Emanuel Berg via Users list for the GNU Emacs text editor
  0 siblings, 1 reply; 3+ messages in thread
From: Óscar Fuentes @ 2021-12-22 16:01 UTC (permalink / raw)
  To: dxlcstar; +Cc: help-gnu-emacs@gnu.org

dxlcstar <dxlcstar@protonmail.com> writes:

> I hope this is not an extremely dumb question.
>
> After installing emacs (mater branch) with native compilation enabled, running
> it for the first time invokes deferred compilation for the packages
> that I call and use, and eln-cache is populated.
>
> But, subsequent invocations of emacs doesn't seem to start deferred
> compilation at all for lisp packages that I didn't use the first time.
>
> I think I am missing something very basic - any suggestions ?


First, check that those packages are really being ignored by
native-comp: if the package has source file foo.el, go to the eln-cache
directory and see if there is foo-####.eln.

Also, check that the source files of those packages are byte-compiled
(to .elc). That's a requirement for generating native code.



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Native compilation
  2021-12-22 16:01 ` Óscar Fuentes
@ 2021-12-23 22:48   ` Emanuel Berg via Users list for the GNU Emacs text editor
  0 siblings, 0 replies; 3+ messages in thread
From: Emanuel Berg via Users list for the GNU Emacs text editor @ 2021-12-23 22:48 UTC (permalink / raw)
  To: help-gnu-emacs

Óscar Fuentes wrote:

> First, check that those packages are really being ignored by
> native-comp: if the package has source file foo.el, go to
> the eln-cache directory and see if there is foo-####.eln.
>
> Also, check that the source files of those packages are
> byte-compiled (to .elc). That's a requirement for generating
> native code.

Uhm, native code, what's that? Compile for the architecture
you're on? But isn't that the natural order of things?

Except for special cases when you cross-compile for, say
a unit with less CPU power, to run but not compile?

And, is that the whole field?

No third way of doing it?

-- 
underground experts united
https://dataswamp.org/~incal




^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2021-12-23 22:48 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2021-12-22 14:41 Native compilation dxlcstar
2021-12-22 16:01 ` Óscar Fuentes
2021-12-23 22:48   ` Emanuel Berg via Users list for the GNU Emacs text editor

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.