GNU bug report logs -
#78783
30.1.50; AOT-compiling site-lisp during the Emacs build doesn't work
Previous Next
Full log
View this message in rfc822 format
> From: Spencer Baugh <sbaugh <at> janestreet.com>
> Cc: acorallo <at> gnu.org, 78783 <at> debbugs.gnu.org, app-emacs-dev <at> janestreet.com
> Date: Fri, 13 Jun 2025 11:41:27 -0400
>
> Eli Zaretskii <eliz <at> gnu.org> writes:
> > severity 78783 wishlist
> > thanks
> >
> >> Cc: Andrea Corallo <acorallo <at> gnu.org>, app-emacs-dev <at> janestreet.com
> >> Date: Fri, 13 Jun 2025 09:34:10 -0400
> >> From: Spencer Baugh via "Bug reports for GNU Emacs,
> >> the Swiss army knife of text editors" <bug-gnu-emacs <at> gnu.org>
> >>
> >>
> >> Native compilation of site-lisp directories during the Emacs build
> >> (e.g. --with-native-compilation=aot) produces .eln files which are
> >> unused when installed.
> >
> > Why are you compiling files in site-lisp during the build? This is
> > not supported, and I see no reason why we should extend our build
> > processes to support it.
> >
> > Why cannot you compile site-lisp files after Emacs is built and
> > installed?
>
> If a site-lisp file is built (whether as part of Emacs or not) and
> subsequently installed into the site-lisp directory, its file name will
> change. That changes the path_hash computed by
> comp-el-to-eln-rel-filename which will cause this issue.
>
> This is a general problem with AOT-compiling files which are
> subsequently installed somewhere else. It applies both for core Emacs
> files and for site-lisp.
No, core Emacs files are okay and supported.
It's compiling site-lisp files in this way is not supported. And you
still haven't answered my question: why do you need that?
The supported way of compiling site-lisp files is after they are
installed in site-lisp.
This bug report was last modified 2 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.