unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo <akrl@sdf.org>
To: emacs-devel@gnu.org
Subject: Re: feature/native-comp, comp-deferred-compilation: no recompilation when .elc newer than .eln?
Date: Sat, 16 May 2020 13:23:09 +0000	[thread overview]
Message-ID: <xjf3680dneq.fsf@sdf.org> (raw)
In-Reply-To: <87ftc0nqtv.fsf@no.workgroup> (Gregor Zattler's message of "Sat,  16 May 2020 11:59:08 +0200")

Gregor Zattler <telegraph@gmx.net> writes:

> Hi Andrea,
> * Andrea Corallo <akrl@sdf.org> [2020-05-16; 07:30]:
>> Gregor Zattler <telegraph@gmx.net> writes:
>>>> Is it possible that the old eln is still being loaded because
>>>> load-prefer-newer is nil?
>>>
>>> load-prefer-newer is t in my case.  The stale org.eln file
>>> was loaded instead of the newer org.elc and the newer
>>> org.elc wasn't compiled to a newer org.eln file.  I realized
>>> because I experienced a specific bug although there was a
>>> patch with a fix in the repo.
>
>> the bit I'm missing is how the load was performed after org is updated.
>> Restarting Emacs or calling `load'?
>
> Sorry for not being more precise: I restart
> emacs after upgrading emacs or org-mode (or notmuch).

I reproduced here.  The problem is apparently that the .eln is always
preferred to the .elc for being loaded regardless `load-prefer-newer'
value, therefore the .eln is loaded directly and no deferred compilation
is triggerd.

I'll have look for a patch.

Thanks

  Andrea

-- 
akrl@sdf.org



  reply	other threads:[~2020-05-16 13:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15 13:10 feature/native-comp, comp-deferred-compilation: no recompilation when .elc newer than .eln? Gregor Zattler
2020-05-15 19:43 ` Andrea Corallo
2020-05-15 21:57   ` Gregor Zattler
2020-05-16  7:30     ` Andrea Corallo
2020-05-16  9:59       ` Gregor Zattler
2020-05-16 13:23         ` Andrea Corallo [this message]
2020-06-06 21:51         ` Andrea Corallo
2020-06-09  6:17           ` Gregor Zattler
2020-06-10 20:29             ` Gregor Zattler
2020-06-11 19:05               ` Andrea Corallo

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=xjf3680dneq.fsf@sdf.org \
    --to=akrl@sdf.org \
    --cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).