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: [External] : Re: Native compilation
Date: Thu, 13 Jan 2022 08:28:23 +0100 [thread overview]
Message-ID: <87zgo0xffs.fsf@zoho.eu> (raw)
In-Reply-To: 83iluo3ykg.fsf@gnu.org
Eli Zaretskii wrote:
>> Yes, but that's completely natural ... good, even?
>
> Quite a few people are annoyed by the many warnings they get
> in this case.
I didn't get a single one except the one from the MELPA
Emacs-w3m and the .emacs case described already. I guess my
144 files are pretty good ...
>>> Natively-compiling Lisp files also means you'll need to
>>> have the original Lisp files around, or else Emacs will
>>> refuse to load the .eln file. If you compress the source
>>> file, you need to have Emacs built with decompression
>>> support (zlib), otherwise Emacs will refuse to load the
>>> .eln file, claiming that the source isn't available.
>>
>> Okay, why?
>
> Because Emacs needs to be sure the .eln file corresponds to
> the .el/.elc, otherwise the session might crash.
OK, well not a problem anyway since it is just source ...
bunch of chars LOL
>> .eln files do exist in
>> ~/.emacs.d/eln-cache/29.0.50-9e08bfb0 including my files,
>> e.g. time-incal-760bfd05-7cbfad50.eln - okay, so maybe
>> that's why I got the warning/error for just one file,
>> .emacs - because .emacs is named .emacs and not emacs.el?
>
> If you have .emacs.elc somewhere, and it said it couldn't find the
> source of it, then that's the reason.
It is ... with .emacs.el symlinked I don't get a warning.
> If you don't have .emacs.elc
Grep the backlog for the answer to this question ...
--
underground experts united
https://dataswamp.org/~incal
prev parent reply other threads:[~2022-01-13 7:28 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
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 [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=87zgo0xffs.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).