Re: Sharing native-lisp system load-path between builds

[Eli Zaretskii]

> From: Björn Bidar <bjorn.bidar@thaodan.de>
> Cc: acorallo@gnu.org,  emacs-devel@gnu.org
> Date: Mon, 14 Aug 2023 13:04:06 +0300
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> From: Björn Bidar <bjorn.bidar@thaodan.de>
> >> Cc: Eli Zaretskii <eliz@gnu.org>,  emacs-devel@gnu.org
> >> Date: Mon, 14 Aug 2023 02:47:23 +0300
> >> 
> >> Andrea Corallo <acorallo@gnu.org> writes:
> >> 
> >> > The hash depends on the set of C primitives present in Emacs.  If the
> >> > hash differs it means your configurations are producing Emacsen with
> >> > different sets of primitives, and this makes eln files incompatible.
> >> 
> >> OK but so why did work with the commit
> >> 3c8167ec0f9647e6fc33e65b0a0324f96cb795ee and before?
> >> 
> >> Nothing has changed in the build environment except the commits between
> >> good commit and d46a2fa319808963bbe8d3a90e7dbb13fcd844f5 or later.
> >
> > What exactly did work back then?  Please describe in detail what you
> > did that worked before 3c8167ec0f9647e6fc33e65b0a0324f96cb795ee and
> > doesn't work now.
> 
> Building Emacs once without X11, then X11 Without GTK and PGTK all with
> native-compilation=aot.
> 
> When packaging Emacs using the precompiled eln from the last build Emacs
> for all the build variants.
> 
> The spec file can be found here:
> https://build.opensuse.org/package/view_file/home:Thaodan:emacs/emacs/emacs.spec?expand=1
> 
> The build process starts at line 319.

Thanks.  So what does "work" and "does not work" mean in this context?