unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Gregor Zattler <telegraph@gmx.net>
To: emacs-devel@gnu.org
Subject: Re: feature/native-comp, comp-deferred-compilation: no recompilation when .elc newer than .eln?
Date: Wed, 10 Jun 2020 22:29:22 +0200	[thread overview]
Message-ID: <87wo4epsv1.fsf@no.workgroup> (raw)
In-Reply-To: <87pna8rceq.fsf@no.workgroup>

Hi Andrea,
* Gregor Zattler <telegraph@gmx.net> [2020-06-09; 08:17]:
> * Andrea Corallo <akrl@sdf.org> [2020-06-06; 21:51]:
>> This issue should be fixed by Nico's patch e38678b268 "Reduce the number
>> of files probed when finding a lisp file."
>>
>> Hope works for you, in case does not please complain :)
>
> I will test in the next days.

it worked, but only after the 3rd invokation of emacs:

1. I recompiled emacs, checked out an old version of org
   mode with a certain bug, compiled that, used it with the
   new emacs, this produced an org.eln file with the
   specific bug.  Which I experienced while using org-mode.

2. I killed emacs, checked out newest org-mode, compiled it,
   started emacs, used org-mode, org.el was not shown in the
   async compile buffer, and the bug was still present and
   the eln file was older than the el an elc files.

3. I killed emacs, started it again, used an org-file, now
   org.el showed up in the async compile buffer, but the eln
   file was as old as before and the bug was present.

4. I killed emacs.  Had a look again for the org.el[cn]?
   files: now the eln file was newest, I used org-mode and
   the bug was gone.

I understand, that a new elc file is used in emacs, the
compilation to eln happens async and when finished the eln
file is not loaded over the elc file.  Therefore I have to
restart emacs in order to actually use the eln file.

I do not understand why my org-usage in step 2 didn't
trigger the compilation of the eln file.

Reloading the eln file instead of the already loaded elc in
3 would be cool, but not that important, since the elc file
is feature-wise equivalent with the eln fiie.


Ciao; Gregor
--
 -... --- .-. . -.. ..--.. ...-.-




  reply	other threads:[~2020-06-10 20:29 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
2020-06-06 21:51         ` Andrea Corallo
2020-06-09  6:17           ` Gregor Zattler
2020-06-10 20:29             ` Gregor Zattler [this message]
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=87wo4epsv1.fsf@no.workgroup \
    --to=telegraph@gmx.net \
    --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).