From: Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>,
Mekeor Melire <mekeor@posteo.de>
Cc: cox.katherine.e+guix@gmail.com, 66864@debbugs.gnu.org, andrew@trop.in
Subject: bug#66864: emacs-build-system builds .eln-files with mismatching path-hashes
Date: Thu, 09 Nov 2023 12:21:20 +0100 [thread overview]
Message-ID: <878r776ukv.fsf@jpoiret.xyz> (raw)
In-Reply-To: <6988d23f1bc6f85e6322d3b97138e3faf4944b88.camel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 944 bytes --]
Hi,
Liliana Marie Prikler <liliana.prikler@gmail.com> writes:
> Am Donnerstag, dem 02.11.2023 um 08:13 +0000 schrieb Mekeor Melire:
>>
>> 2023-11-01 15:16 liliana.prikler@gmail.com:
>>
>> > I think Emacs might be calculating its own hash at runtime
>> > rather than baking in the value at build time.
>>
>> Exactly. That's what I was trying to express.
> I'm not sure whether this is reproducible. On my system
> $ guix build emacs-dash --with-input=emacs-minimal=emacs
> /gnu/store/zr16hd25338imljqxxfsf07smbfv3wxd-emacs-dash-2.19.1
> $ ls /gnu/store/zr16hd25338imljqxxfsf07smbfv3wxd-emacs-dash-2.19.1/lib/emacs/native-site-lisp
> 29.1-e9e5c1ce
> $ emacs --batch --eval='(message "%s" comp-abi-hash)'
> e9e5c1ce
> Looks like everything's alright?
It's the .eln file itself that has the hash of the .el's path in its
name. That's computed by `comp-el-to-eln-filename`.
Best,
--
Josselin Poiret
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]
next prev parent reply other threads:[~2023-11-09 11:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 23:49 bug#66864: emacs-build-system builds .eln-files with mismatching path-hashes Mekeor Melire
2023-11-01 11:52 ` Liliana Marie Prikler
2023-11-01 13:03 ` Mekeor Melire
2023-11-01 14:16 ` Liliana Marie Prikler
2023-11-02 8:13 ` Mekeor Melire
2023-11-09 10:54 ` Liliana Marie Prikler
2023-11-09 11:21 ` Josselin Poiret via Bug reports for GNU Guix [this message]
2023-11-09 12:03 ` Liliana Marie Prikler
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878r776ukv.fsf@jpoiret.xyz \
--to=bug-guix@gnu.org \
--cc=66864@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=cox.katherine.e+guix@gmail.com \
--cc=dev@jpoiret.xyz \
--cc=liliana.prikler@gmail.com \
--cc=mekeor@posteo.de \
/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/guix.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).