Re: 29.2: (void-function batch-update-autoloads)

[Uwe Brauer <oub@mat.ucm.es>]

[-- Attachment #1: Type: text/plain, Size: 2764 bytes --]

>>> "EZ" == Eli Zaretskii <eliz@gnu.org> writes:

>> ,----
>> | 
>> | EMACS=/usr/local/bin/emacs
>> | EMACSFLAGS=-batch --no-site-file --eval '(setq debug-on-error t)'
>> | 
>> | autoloads: 
>> | 	$(EMACS) $(EMACSFLAGS) $(addprefix -L ,$(LOADPATH)) --eval
>> | '(setq generated-autoload-file "$(abspath $(LOADDEFS))")' -f
>> | loaddefs-generate--emacs-batch $(abspath $(LOADDIRS))
>> `----

> I don't know where did you take this from.  In Emacs 29.2,
> lisp/Makefile says something very different:

This is from our Makefile. I am not 100% sure who wrote this. Git
(mercurial) seems to indicate that it was Eric Ludlam.



>   autoloads: $(lisp)/emacs-lisp/loaddefs-gen.elc gen-lisp
> 	  $(AM_V_GEN)$(emacs) \
> 	      -l $(lisp)/emacs-lisp/loaddefs-gen.elc \
> 	      -f loaddefs-generate--emacs-batch ${SUBDIRS_ALMOST}

>> Using 29.2, but I receive still, 
>> (void-function loaddefs-generate--emacs-batch)

> And what is the textbook solution in Emacs for void-function errors?

Asking in the list 😉? ok seriously now, loading the file that defines
that function, which the above code seems to do, if I take a closer look.

But now I am deeply confused.

I thought in a Makefile, that, among other things, byte compile lisp files,
one should best set

EMACSFLAGS=-batch --no-site-file 

or something similar and the generation of autoloads would use
functionalities of emacs core.

As you can see in our case the generation of autoloads was done with 

--8<---------------cut here---------------start------------->8---
autoloads: 
	$(EMACS) $(EMACSFLAGS) $(addprefix -L ,$(LOADPATH)) --eval '(setq generated-autoload-file "$(abspath $(LOADDEFS))")' -f batch-update-autoloads $(abspath $(LOADDIRS))
--8<---------------cut here---------------end--------------->8---

While in your example a lisp file is needed to be loaded.

Now the problem is that we want to cater for users with different Emacs
versions 30,29,28, 27 and maybe even 26.

In the case of lisp file, I know how to deal with such a situation, but
for a Makefile? Shall we add a .configure file now to find out which
emacs version is used and then distinguish in the Makefile whether it is
<29 or >=29?



>> That being said I just wished, that there would be a more centralised
>> file or directory, where obsolete functions and variables were listed.

> The lisp/obsolete/ directory is home for all such functions and
> variables.


Ok I should have a close look then.


-- 
I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the EU and NATO membership of Ukraine. 


[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5684 bytes --]