unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <moasenwood@zoho.eu>
To: help-gnu-emacs@gnu.org
Subject: Source file '.../killer-source.el' newer than byte-compiled file
Date: Tue, 23 Apr 2019 19:39:34 +0200	[thread overview]
Message-ID: <8636m8ipt5.fsf@zoho.eu> (raw)

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?

What it says isn't radical, because isn't that
the way make(1) works, you have a target, and
a source, and if the source is newer
(i.e. more recently modified) than the target,
that means it has been edited since last
compilation, i.e., (re)compilation
should happen?

Why am I told this specifically, and why for
just certain files, not every one I edit?

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?

If this theory is correct (?), do you even need
to compile one more time to get rid of the
message? Because at that time a.el hasn't been
changed, so it won't be recompiled, and thus
won't get access to the new b.elc anyway?

Only this in turn doesn't matter either in
practise as long as there is no change to the
interface of b, because when the user uses
b thru a, it'll still get the latest b.elc?


[1] http://user.it.uu.se/~embe8573/emacs-init/Makefile

-- 
underground experts united
http://user.it.uu.se/~embe8573




             reply	other threads:[~2019-04-23 17:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-23 17:39 Emanuel Berg [this message]
2019-04-23 17:49 ` Source file '.../killer-source.el' newer than byte-compiled file Eli Zaretskii
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=8636m8ipt5.fsf@zoho.eu \
    --to=moasenwood@zoho.eu \
    --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).