Re: feature/native-comp, comp-deferred-compilation: no recompilation when .elc newer than .eln?

[Andrea Corallo <akrl@sdf.org>]

Gregor Zattler <telegraph@gmx.net> writes:

>> I'm not sure the sequence of events is clear to me, especially how the
>> the new org was loaded after it was compiled calling make.
>
> I use org-mode from git.  Org-mode has a build system and
> esypecially `make up1` does a git pull, compile , builds
> documentation and runs checks.  I do this from time to time.
>
> The relevant part of the git repo is in my emacs load-path:
>
> (add-to-list 'load-path (expand-file-name "~/src/org-mode/lisp"))
> (setq load-path (cons "~/src/org-mode/contrib/lisp/" load-path))
>
>> Deferred compilation logic to date works as follow: if an elc is being
>> loaded, is lexical and the corresponding source is found, then an async
>> compilation is queued.  No file date is taken in account.
>>
>> 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.
>
> Thanks, Gregor

Hi Gregor,

the bit I'm missing is how the load was performed after org is updated.
Restarting Emacs or calling `load'?

Thanks

  Andrea

-- 
akrl@sdf.org