From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: [External] : Re: Native compilation
Date: Sun, 09 Jan 2022 09:13:38 +0200 [thread overview]
Message-ID: <83czl12xgd.fsf@gnu.org> (raw)
In-Reply-To: <87ilutv5sb.fsf@zoho.eu> (message from Emanuel Berg via Users list for the GNU Emacs text editor on Sun, 09 Jan 2022 06:26:12 +0100)
> Date: Sun, 09 Jan 2022 06:26:12 +0100
> Cc: emacs-w3m@namazu.org
> From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
>
> Eli Zaretskii wrote:
>
> >> Here is what it said during the native compile:
> >>
> >> Warning (comp): Cannot look-up eln file as no source file
> >> was found for /home/incal/.emacs.elc
> >
> > The former means your .emacs was not natively compiled
> > (which is generally a Good Thing).
>
> Thanks, you mean not to compile it natively or not compile it
> at all?
Natively.
> But the strange thing is it _is_ compiled, there is an
> .emacs.elc which according to file(1) is "Emacs/XEmacs v28
> byte-compiled Lisp data", however the Emacs that compiled [1]
> it is actually
The native compilation didn't happen because Emacs didn't find the
source file for the .elc file. I'm saying that you shouldn't worry
about that: native compilation of init files can only cause trouble,
and will never provide any tangible performance boost. So just
disregard that warning.
> So I wonder if there is some special way to compile it
> natively?
Maybe. But why bother?
> I mean for all the extra Elisp one might have in HOME?
I don't think it's relevant.
> >> Warning (comp): w3m.el:93:1: Warning: Variable
> >> ‘w3m-fb-mode’ left uninitialized Disable showing
> >
> > The latter means you need to look for a missing 'require'.
>
> It is in the MELPA's Emacs-w3m, I think, version 1.4.632.
Report a bug to the developers.
next prev parent reply other threads:[~2022-01-09 7:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-24 0:44 [External] : Re: Native compilation Drew Adams
2021-12-24 2:53 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-12-24 4:06 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-12-29 13:52 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-12-31 8:59 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-12-31 9:04 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-12-31 12:18 ` Eli Zaretskii
2021-12-31 12:31 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-12-31 12:46 ` Eli Zaretskii
2021-12-31 13:00 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-12-31 13:08 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-12-31 13:37 ` Eli Zaretskii
2021-12-31 13:02 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-12-31 13:38 ` Eli Zaretskii
2022-01-09 5:26 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-09 7:13 ` Eli Zaretskii [this message]
2022-01-10 13:23 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-10 17:51 ` Eli Zaretskii
2022-01-11 13:18 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-11 17:04 ` Eli Zaretskii
2022-01-12 22:38 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-12 22:49 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-13 7:07 ` Eli Zaretskii
2022-01-13 7:31 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-13 7:34 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-13 7:05 ` Eli Zaretskii
2022-01-13 7:28 ` Emanuel Berg via Users list for the GNU Emacs text editor
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=83czl12xgd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).