Re: Finalizing 'inhibit-automatic-native-compilation'

[Eli Zaretskii]

> From: Lynn Winebarger <owinebar@gmail.com>
> Date: Mon, 6 Feb 2023 09:29:10 -0500
> Cc: Andrea Corallo <akrl@sdf.org>, Stefan Monnier <monnier@iro.umontreal.ca>, 
>       emacs-devel <emacs-devel@gnu.org>
> 
>  No, I'm saying that starting Emacs assumes the dumped *.eln files live
>  in one of two possible locations, and you must make sure they are in
>  one of those two locations, or else Emacs will fail to start.
> 
> Then I'm confused by what you mean by "re-dumping" above.  I'm only 
> referencing the result of starting
> temacs in dump-mode.

You started the re-dumping subject (although the current discussion is
about something completely different).

> Andreas may well be correct that there are no additional challenges for 
> native-compiled libraries than there
> would be for byte-compiled, aside from the part of the build process ensuring 
> those eln files exist in the right
> location that you note.  But since dump-portable-emacs is available for the 
> byte-compiled case, these
> limitations are most noticable for someone attempting to dump native-compiled 
> libraries. 
> 
> As soon as a library requiring cl-lib is included, the prohibition (in 
> dump-mode) against autoloading and
> circular requires is a problem.  

Sorry, this is unrelated to the issue at hand, and was already
discussed in the past, so if you want still to discuss it, please
start a new thread.