From: Mekeor Melire <mekeor@posteo.de>
To: 69201@debbugs.gnu.org
Subject: bug#69201: Emacs master-branch renamed comp-write-bytecode-file which emacs-utils depends on
Date: Thu, 15 Feb 2024 22:23:13 +0000 [thread overview]
Message-ID: <87sf1tz5se.fsf@posteo.de> (raw)
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@gnu.org>
AuthorDate: Sun Feb 11 12:31:13 2024 +0100
Commit: Andrea Corallo <acorallo@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
next reply other threads:[~2024-02-18 18:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 22:23 Mekeor Melire [this message]
2024-02-19 21:18 ` bug#69201: Emacs master-branch renamed comp-write-bytecode-file which emacs-utils depends on Liliana Marie Prikler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sf1tz5se.fsf@posteo.de \
--to=mekeor@posteo.de \
--cc=69201@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).