From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Source file '.../killer-source.el' newer than byte-compiled file
Date: Tue, 23 Apr 2019 20:49:30 +0300 [thread overview]
Message-ID: <8336m84no5.fsf@gnu.org> (raw)
In-Reply-To: <8636m8ipt5.fsf@zoho.eu> (message from Emanuel Berg on Tue, 23 Apr 2019 19:39:34 +0200)
> From: Emanuel Berg <moasenwood@zoho.eu>
> Date: Tue, 23 Apr 2019 19:39:34 +0200
>
> Often when I do some changes to Elisp files and
> then run the byte-compiler with the following
> Makefile [1] I get this message for several
> files, but not all of them, and not always:
>
> Source file '~/path/to/killer-source.el' newer
> than byte-compiled file
>
> But what is the purpose of this message and why
> is it so capricious in terms of when
> it appears?
Its purpose is to tell you that Emacs loads a .elc file that is older
than the corresponding .el file. See load-prefer-newer.
> Why am I told this specifically, and why for
> just certain files, not every one I edit?
It depends on the order of byte-compilation.
> Has it to do with files being `require'd before
> compilation has gotten that far? So if a.el is
> compiled into a.elc, but a requires b, only at
> that time b.elc hasn't been compiled *but* b.el
> has been edited?
Yes.
next prev parent reply other threads:[~2019-04-23 17:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 17:39 Source file '.../killer-source.el' newer than byte-compiled file Emanuel Berg
2019-04-23 17:49 ` Eli Zaretskii [this message]
2019-04-23 18:32 ` Emanuel Berg
2019-04-23 18:39 ` Emanuel Berg
2019-04-23 19:03 ` Eli Zaretskii
2019-04-23 22:42 ` Emanuel Berg
2019-04-23 23:17 ` Nick Dokos
2019-04-24 0:18 ` Emanuel Berg
2019-04-24 1:33 ` Emanuel Berg
2019-04-24 6:24 ` Eli Zaretskii
2019-04-25 3:25 ` `eval-when-compile' and circular dependencies (was: Re: Source file '.../killer-source.el' newer than byte-compiled file) Emanuel Berg
2019-04-25 6:37 ` Eli Zaretskii
2019-04-25 7:03 ` Emanuel Berg
2019-04-25 8:43 ` Eli Zaretskii
2019-04-23 19:02 ` Source file '.../killer-source.el' newer than byte-compiled file Eli Zaretskii
2019-04-23 22:59 ` Emanuel Berg
2019-04-23 18:02 ` Emanuel Berg
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=8336m84no5.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).