unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
* bug#69201: Emacs master-branch renamed comp-write-bytecode-file which emacs-utils depends on
@ 2024-02-15 22:23 Mekeor Melire
  2024-02-19 21:18 ` Liliana Marie Prikler
  0 siblings, 1 reply; 2+ messages in thread
From: Mekeor Melire @ 2024-02-15 22:23 UTC (permalink / raw)
  To: 69201

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




^ permalink raw reply	[flat|nested] 2+ messages in thread

* bug#69201: Emacs master-branch renamed comp-write-bytecode-file which emacs-utils depends on
  2024-02-15 22:23 bug#69201: Emacs master-branch renamed comp-write-bytecode-file which emacs-utils depends on Mekeor Melire
@ 2024-02-19 21:18 ` Liliana Marie Prikler
  0 siblings, 0 replies; 2+ messages in thread
From: Liliana Marie Prikler @ 2024-02-19 21:18 UTC (permalink / raw)
  To: Mekeor Melire, 69201

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@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.
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




^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2024-02-19 21:42 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-02-15 22:23 bug#69201: Emacs master-branch renamed comp-write-bytecode-file which emacs-utils depends on Mekeor Melire
2024-02-19 21:18 ` Liliana Marie Prikler

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).