From: Eli Zaretskii <eliz@gnu.org>
To: "Björn Bidar" <bjorn.bidar@thaodan.de>
Cc: acorallo@gnu.org, emacs-devel@gnu.org
Subject: Re: Sharing native-lisp system load-path between builds
Date: Mon, 14 Aug 2023 21:41:58 +0300 [thread overview]
Message-ID: <83zg2ta2kp.fsf@gnu.org> (raw)
In-Reply-To: <87bkf932b5.fsf@thaodan.de> (message from Björn Bidar on Mon, 14 Aug 2023 21:29:34 +0300)
[Why private email?]
> From: Björn Bidar <bjorn.bidar@thaodan.de>
> Date: Mon, 14 Aug 2023 21:29:34 +0300
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Thanks. So what does "work" and "does not work" mean in this context?
>
> Work means the eln files could be shared, doesn't mean the files can't
> be shared the hash in the native lisp path is different and the files
> are no longer compatible.
How did you share them? did you manually copy them into the same
directory or forced Emacs to write them there? Or did Emacs create
*.eln files with the same hashes and in the same 29.0.50-NNNNN
subdirectory? Also, which *.el files were compiled into *.eln files
you could share -- were those the preloaded *.el files, non-preloaded
*.el files from the Emacs tree, or third-party *.el files from
packages that are not bundled with Emacs?
In general, such different configurations could only be able to share
*.eln files by sheer luck. It is enough to have one more or one less
primitive in one of the builds to require a separate set of *.eln
files, because the hash of the versioned subdirectory of native-lisp/
and of eln-cache changes when primitives are added or deleted. That
has been so for a very long time, definitely long before commit
3c8167ec0f964.
next prev parent reply other threads:[~2023-08-14 18:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 0:14 Sharing native-lisp system load-path between builds Björn Bidar
2023-06-26 2:31 ` Eli Zaretskii
2023-06-26 4:26 ` Björn Bidar
2023-06-26 7:12 ` Andrea Corallo
2023-08-13 23:47 ` Björn Bidar
2023-08-14 2:29 ` Eli Zaretskii
2023-08-14 10:04 ` Björn Bidar
2023-08-14 12:24 ` Eli Zaretskii
[not found] ` <87bkf932b5.fsf@thaodan.de>
2023-08-14 18:41 ` Eli Zaretskii [this message]
2023-08-16 7:44 ` Björn Bidar
2023-08-16 8:49 ` Andrea Corallo
2023-08-18 22:23 ` Björn Bidar
2023-08-19 6:21 ` Eli Zaretskii
2023-09-26 14:26 ` Sharing native-lisp system load-path between builds, my own error Björn Bidar
2023-06-26 11:18 ` Sharing native-lisp system load-path between builds 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83zg2ta2kp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acorallo@gnu.org \
--cc=bjorn.bidar@thaodan.de \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.