unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Björn Bidar" <bjorn.bidar@thaodan.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Gerd Möllmann" <gerd.moellmann@gmail.com>, emacs-devel@gnu.org
Subject: Re: How to make aot native-compilation and pdmp creation reproduceable
Date: Mon, 09 Oct 2023 17:48:05 +0300	[thread overview]
Message-ID: <87fs2jua1m.fsf@thaodan.de> (raw)
In-Reply-To: <83il7gvt6m.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 09 Oct 2023 16:09:21 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Gerd Möllmann <gerd.moellmann@gmail.com>
>> Cc: bjorn.bidar@thaodan.de,  emacs-devel@gnu.org
>> Date: Mon, 09 Oct 2023 13:55:30 +0200
>> 
>> Eli Zaretskii <eliz@gnu.org> writes:
>> 
>> >> My hypothesis is that x-win.eln changes between builds (print-circle
>> >> etc.) => make-fingerprint computes a different ingerprint and so on.
>> >
>> > If x-win.el didn't change, x-win.eln will not be regenerated, so
>> > something else is at work here.
>> 
>> But x-win.elc _did_ change.  To cite one of Björn's mails
>
> If x-win.elc or x-win.eln change between builds (meaning x-win.el or
> one of the *.el files it 'require's changed), why do we expect the
> builds to be identical?

x-win.elc didn't change only x-win.eln (and the emacs executeable and pdmp) did. 

All uncompiled and the byte-compiled Emacs Lisp is inside the emacs-el
package which is identical.

See my message here:
https://mail.gnu.org/archive/html/emacs-devel/2023-10/msg00133.html





  parent reply	other threads:[~2023-10-09 14:48 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-07 18:37 How to make aot native-compilation and pdmp creation reproduceable Björn Bidar
2023-10-07 19:27 ` Gerd Möllmann
2023-10-08 20:53   ` Björn Bidar
2023-10-08 20:57   ` Björn Bidar
2023-10-09  4:19     ` Gerd Möllmann
2023-10-09 11:05       ` Eli Zaretskii
2023-10-09 11:26         ` Gerd Möllmann
2023-10-09 11:32           ` Eli Zaretskii
2023-10-09 11:55             ` Gerd Möllmann
2023-10-09 12:29               ` Gerd Möllmann
2023-10-09 13:09               ` Eli Zaretskii
2023-10-09 13:33                 ` Gerd Möllmann
2023-10-09 14:20                   ` Eli Zaretskii
2023-10-09 14:30                     ` Gerd Möllmann
2023-10-09 14:48                 ` Björn Bidar [this message]
2023-10-09 14:58                   ` Eli Zaretskii
2023-10-09 15:44                     ` Björn Bidar
2023-10-09 14:52           ` Björn Bidar
2023-10-09 15:06             ` Gerd Möllmann
     [not found]               ` <8734yju8ax.fsf@thaodan.de>
2023-10-09 15:59                 ` Eli Zaretskii
2023-10-09 16:06                   ` Björn Bidar
2023-10-09 16:28                     ` Eli Zaretskii
2023-10-09 16:53                       ` Björn Bidar
2023-10-09 16:40                 ` Gerd Möllmann
2023-10-09 17:06                   ` Björn Bidar
2023-10-09 17:19                     ` Gerd Möllmann
2023-10-09 18:23                       ` Alan Mackenzie
2023-10-10  6:21                         ` Gerd Möllmann
2023-10-10 10:39                           ` Alan Mackenzie
2023-10-10 11:12                             ` Gerd Möllmann
2023-10-10 11:58                             ` Michael Albinus
2023-10-10 12:17                             ` Eli Zaretskii
2023-10-10 13:07                               ` Alan Mackenzie
2023-10-11  9:15                             ` Andrea Corallo
2023-10-10  8:30                         ` Ulrich Mueller
2023-10-10  9:28                           ` Gerd Möllmann
2023-10-10 10:53                             ` Ulrich Mueller
2023-10-10 11:15                               ` Gerd Möllmann
2023-10-10 11:08                           ` Differences in *.elc files (was: Re: How to make aot native-compilation and pdmp creation reproduceable) Ulrich Mueller
2023-10-10 11:51                             ` Differences in *.elc files Gerd Möllmann
2023-10-10 12:14                           ` How to make aot native-compilation and pdmp creation reproduceable Eli Zaretskii
2023-10-10 14:40                             ` Björn Bidar
2023-10-10 14:59                             ` Ulrich Mueller
2023-10-09  4:28     ` Gerd Möllmann
2023-10-08  7:14 ` Andrea Corallo
2023-10-08 21:38   ` Björn Bidar
2023-10-09  2:34     ` Eli Zaretskii
2023-10-09  4:25       ` Björn Bidar
2023-10-09  4:46         ` Gerd Möllmann
2023-10-09  5:06           ` Gerd Möllmann
2023-10-09  5:47             ` Gerd Möllmann
2023-10-09 11:15         ` 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=87fs2jua1m.fsf@thaodan.de \
    --to=bjorn.bidar@thaodan.de \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=gerd.moellmann@gmail.com \
    /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).