all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: "Björn Bidar" <bjorn.bidar@thaodan.de>
Cc: Eli Zaretskii <eliz@gnu.org>,  emacs-devel@gnu.org
Subject: Re: How to make aot native-compilation and pdmp creation reproduceable
Date: Mon, 09 Oct 2023 18:40:05 +0200	[thread overview]
Message-ID: <m2ttqzn40q.fsf@Pro.fritz.box> (raw)
In-Reply-To: <8734yju8ax.fsf@thaodan.de> ("Björn Bidar"'s message of "Mon, 09 Oct 2023 18:25:42 +0300")

Björn Bidar <bjorn.bidar@thaodan.de> writes:

> Gerd Möllmann <gerd.moellmann@gmail.com> writes:
>
>> Björn Bidar <bjorn.bidar@thaodan.de> writes:
>>
>>>> My hypothesis is that x-win.eln changes between builds (print-circle
>>>> etc.) => make-fingerprint computes a different ingerprint and so on
>>>
>>> But the emacs execute and pdmp even changes for builds without
>>> native-comp, see my earlier message:
>>> https://mail.gnu.org/archive/html/emacs-devel/2023-10/msg00133.html
>>
>> Is that the right link?  Where does it say that that is w/o native-comp?
>> Anyway, so the facts are which now?
>
> The link only contains the diff. I attach the full build log now yes.

To be honest, I don't understand what you mean by the first sentence.
The linked message didn't say it's w/o native-compilation?

>
>> - all builds are from scratch?
>
> Yes they are from scratch in a clean build environment, a open build
> service worker (see attachment).
>
>> - Executable and pdmp change with every build, independent of
>>   native-comp?
> yes
>> - x-win.eln changes with native-comp?
> yes

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?

> Build log without native-comp:

Not of great help, I'm afraid.  Lots of stuff nobody wants to know, here
at least :-).

Anyway--what are these CFLAGS for, esp. -DPDMP_BASE=...?  I don't know
what they do.

> [  187s] + CFLAGS='-O2 -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -flto=auto -g -D_GNU_SOURCE -DGDK_DISABLE_DEPRECATION_WARNINGS -DGLIB_DISABLE_DEPRECATION_WARNINGS -pipe -Wno-pointer-sign -Wno-unused-variable -Wno-unused-label -fno-optimize-sibling-calls -DPDMP_BASE='\''"emacs-wayland"'\'''
> [  187s] + ./configure --disable-build-details ...

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.



  parent reply	other threads:[~2023-10-09 16:40 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2ttqzn40q.fsf@Pro.fritz.box \
    --to=gerd.moellmann@gmail.com \
    --cc=bjorn.bidar@thaodan.de \
    --cc=eliz@gnu.org \
    --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.