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

[Eli Zaretskii <eliz@gnu.org>]

1> From: Björn Bidar <bjorn.bidar@thaodan.de>
> Cc: emacs-devel@gnu.org
> Date: Mon, 26 Jun 2023 07:26:03 +0300
> 
> > It isn't a recent change, at least not in principle.
> 
> What could have change this?

Something either in your build environments or in Emacs itself that
made the different builds incompatible, as far as the *.eln files are
concerned.

> Each build configuration is 100% the same except the optional
> dependencies they are build with.
> 
> There's no change to any source they are build one after the other.

If Emacs decided that they are not compatible, then they aren't.
Using the same source is not enough, since the same sources are used
to produce very different builds: with and without X, with and without
Lucid/GTK, to say nothing of builds for Windows and macOS.  The cause
of these differences in the binaries are the preprocessor directives
and conditions that change the outcome of the build under the control
of the configure script which decides what parts of the sources to
compile into the binary and what parts not to compile.