unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Trey Peacock <me@treypeacock.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	47337@debbugs.gnu.org, Konstantin Reich <reich-cv@yandex.ru>
Subject: bug#47337: 28.0.50; [feature/native-comp] Compilation over and over again
Date: Wed, 24 Mar 2021 14:31:05 +0000	[thread overview]
Message-ID: <xjfzgysr5cm.fsf@sdf.org> (raw)
In-Reply-To: <8735wls1hj.fsf@treypeacock.com> (Trey Peacock's message of "Wed,  24 Mar 2021 02:57:03 +0000")

Trey Peacock <me@treypeacock.com> writes:

> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> From: Konstantin Reich <reich-cv@yandex.ru>
>>> Date: Tue, 23 Mar 2021 11:42:42 +0300
>>>
>>> With recent update, Emacs re-compiles all files over and over again.
>>> So for example in the directory ~/.emacs.d/eln-cache/28.0.50-da68e688
>>> I have file "seq-c314b42f-92293e32.eln". I start emacs and the file is
>>> compiled again. As a result, I have the same file with the
>>> updated timestamp in the same directory.
>>>
>>>
>>> Moreover, I have compiled emacs with "NATIVE_FULL_AOT=1". So i already have
>>> the same file in :
>>> /usr/local/lib/emacs/28.0.50/native-lisp/28.0.50-da68e688/
>>> Still, every time i start emacs, it starts to recompile all files.
>>>
>>> It is never ending cycle of compilation.
>>
>> My problem starts even earlier: dumping Emacs as part of the build
>> doesn't seem to load the preloaded *.eln files, but the *.elc files
>> instead (or at least it doesn't announce the fact that "native
>> compiled lisp" file is loaded), although I do have all the freshly
>> compiled *.eln files under native-lisp/.
>>
>>
>>
>>
>
> I am also experiencing this issue. I've found my comp-eln-load-path
> value is '("~/.emacs.d/eln-cache/" "../native-lisp/"). Notably, the
> system variable looks incorrect since based off the invocation-directory
> it would mean my native-comp files are in /usr/native-lisp/.

Could you be more specific on what's the value of you
`invocation-directory' and where the eln is located?

Thanks

  Andrea





  reply	other threads:[~2021-03-24 14:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-23  8:42 bug#47337: 28.0.50; [feature/native-comp] Compilation over and over again Konstantin Reich
2021-03-23 10:18 ` Eli Zaretskii
2021-03-24 13:33   ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-25  9:12     ` Eli Zaretskii
2021-03-24  2:57 ` Trey Peacock
2021-03-24 14:31   ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-03-24 15:15     ` Trey Peacock
2021-03-24 16:06       ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-25  9:14     ` Eli Zaretskii
2021-03-25 10:12       ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-24 11:44 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-24 15:31   ` Konstantin Reich
2021-03-24 15:48     ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-25  9:12   ` Eli Zaretskii

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=xjfzgysr5cm.fsf@sdf.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=47337@debbugs.gnu.org \
    --cc=akrl@sdf.org \
    --cc=eliz@gnu.org \
    --cc=me@treypeacock.com \
    --cc=reich-cv@yandex.ru \
    /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).