From: Alan Mackenzie <acm@muc.de>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: "Björn Bidar" <bjorn.bidar@thaodan.de>,
"Eli Zaretskii" <eliz@gnu.org>,
emacs-devel@gnu.org
Subject: Re: How to make aot native-compilation and pdmp creation reproduceable
Date: Mon, 9 Oct 2023 18:23:54 +0000 [thread overview]
Message-ID: <ZSRFOvAkEbmr5f_9@ACM> (raw)
In-Reply-To: <m2pm1nn278.fsf@Pro.fritz.box>
Hello, everyone.
On Mon, Oct 09, 2023 at 19:19:23 +0200, Gerd Möllmann wrote:
> Björn Bidar <bjorn.bidar@thaodan.de> writes:
> >> Let me add another question, just to be as precise as possible:
> >>
> >> I understand We have differences between 2 independent builds with
> >> native compilation. When you say executable and pdmp differ without
> >> native compilation, do you mean between 2 builds both without native
> >> comp?
> What about this?
> >> I'd recommend simplifying things by building Emacs with standard options
> >> (no CFLAGS=...) and without any of your build tools. Just 2 clean build
> >> directories, and then compare.
> >
> > I don't think how that simplifies things, cflags don't impact if the
> > build is reproduceable or not.
> You know that I'm not talking about CFLAGS alone?
> But I'm just giving you an advice. You can of course free to ignore it.
For what it's worth, I just built Emacs twice on one of my development
repositories on GNU/Linux, and the two emacsen produced were identical,
checked by cmp and md5sum.
Each build was set off with
$ make -j17 bootstrap
.. My configuration was created by:
$ configure --with-gpm --with-native-compilation --with-gif=no --with-tiff=no
.. Maybe I don't understand what the problem is, but I'm seeing
repeatable builds.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2023-10-09 18:23 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZSRFOvAkEbmr5f_9@ACM \
--to=acm@muc.de \
--cc=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 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.