From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Native compilation
Date: Thu, 23 Dec 2021 23:48:19 +0100 [thread overview]
Message-ID: <87zgor9bv0.fsf@zoho.eu> (raw)
In-Reply-To: 87czloy6ga.fsf@telefonica.net
Ó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
prev parent reply other threads:[~2021-12-23 22:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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=87zgor9bv0.fsf@zoho.eu \
--to=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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.
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).