Subject: Re: Emacs master-branch renamed comp-write-bytecode-file which emacs-utils depends on

From: Liliana Marie Prikler <[email-masked]>
Date: Mon, 19 Feb 2024 22:18:13 +0100

Am Donnerstag, dem 15.02.2024 um 22:23 +0000 schrieb Mekeor Melire:
> On Emacs' master-branch, the emacs-lisp function
> comp-write-bytecode-file has been renamed to comp--write-bytecode-
> file (i.e. to include a double dash) in this commit [1]:
> 
>     faa46eb8667c11a0725500a50e957eb78021c99f
>     Author:     Andrea Corallo <[email-masked]>
>     AuthorDate: Sun Feb 11 12:31:13 2024 +0100
>     Commit:     Andrea Corallo <[email-masked]>
>     CommitDate: Sun Feb 11 15:26:12 2024 +0100
> 
>     Rename a number of native compiler functions
> 
> Guix' function emacs-compile-directory from module (guix build
> emacs-utils) [2] depends on this emacs-lisp function.
> 
> Thus, when emacs-next-minimal is build from the above mentioned
> commit or later, it won't be possible to build packages that use
> emacs-build-system, when using
> --with-input=emacs-minimal=emacs-next-minimal, or in Guile code,
> argument "#:emacs emacs-next-minimal". This might be considered to be
> a minor issue as of right now.
> 
> It'll become a more general problem, when Emacs 30 is released.
Thanks for the heads-up.  Assuming the calling convention stays the
same, this should be easy to work around (using fboundp and resolving
to the right symbol).  Unfortunately, I have other work to experiment
on emacs-team right now, so if you find this pressing, I encourage you
to submit your own patch (against emacs-team, for the particular
procedure in emacs-utils).

Cheers