GNU bug report logs -
#69201
Emacs master-branch renamed comp-write-bytecode-file which emacs-utils depends on
Previous Next
To reply to this bug, email your comments to 69201 AT debbugs.gnu.org.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#69201
; Package
guix
.
(Sun, 18 Feb 2024 18:22:12 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Mekeor Melire <mekeor <at> posteo.de>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Sun, 18 Feb 2024 18:22:12 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
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 <acorallo <at> gnu.org>
AuthorDate: Sun Feb 11 12:31:13 2024 +0100
Commit: Andrea Corallo <acorallo <at> gnu.org>
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.
[1] https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=faa46eb8667c11a0725500a50e957eb78021c99f
[2] https://git.savannah.gnu.org/cgit/guix.git/tree/guix/build/emacs-utils.scm?h=08ed3ec64ecd571d92d497b2493f5c0225102c99#n153
Information forwarded
to
bug-guix <at> gnu.org
:
bug#69201
; Package
guix
.
(Mon, 19 Feb 2024 21:20:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 69201 <at> debbugs.gnu.org (full text, mbox):
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 <acorallo <at> gnu.org>
> AuthorDate: Sun Feb 11 12:31:13 2024 +0100
> Commit: Andrea Corallo <acorallo <at> gnu.org>
> 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
This bug report was last modified 1 year and 85 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.