auctex-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [can't compile the main branch]: SOLVED


From: Arash Esbati
Subject: Re: [can't compile the main branch]: SOLVED
Date: Thu, 25 Apr 2024 12:35:40 +0200
User-agent: Gnus/5.13 (Gnus v5.13)

Tassilo Horn <tsdh@gnu.org> writes:

> Done.

Thanks.  Do you mind if I add this change to it:

--8<---------------cut here---------------start------------->8---
diff --git a/GNUmakefile b/GNUmakefile
index 892d1c3c..999861cb 100644
--- a/GNUmakefile
+++ b/GNUmakefile
@@ -83,7 +83,8 @@ clean:
        rm -f $(ALL_GENERATED_FILES) \
                $(wildcard *.elc style/*.elc) \
                auctex-autoloads.el \
-               ChangeLog
+               ChangeLog \
+               $(DYNVARSFILES)

 # Copied&adapted from doc/Makefile.in.
 MAKEINFO_PLAIN=$(MAKEINFO) -D rawfile --no-headers
@@ -138,12 +139,12 @@ $(LATEX_FILES): latex/preview.dtx latex/bootstrap.ins

 DYNVARSFILES = *.dynvars style/*.dynvars auctex-dynvars
 dynvars-check:
-       rm -f $(wildcard *.elc) $(wildcard style/*elc) $(DYNVARSFILES)
+       rm -f $(wildcard *.elc) $(wildcard style/*.elc) $(DYNVARSFILES)
        EMACS_GENERATE_DYNVARS=1 $(EMACS) -f batch-byte-compile \
-               $(wildcard *.el) $(wildcard style/*el) \
+               $(wildcard *.el) $(wildcard style/*.el) \
                > /dev/null 2>&1
        cat *.dynvars style/*.dynvars > auctex-dynvars
-       rm -f $(wildcard *.elc) $(wildcard style/*elc)
+       rm -f $(wildcard *.elc) $(wildcard style/*.elc)
        EMACS_DYNVARS_FILE=auctex-dynvars $(EMACS) \
                -f batch-byte-compile \
-               $(wildcard *.el) $(wildcard style/*el)
+               $(wildcard *.el) $(wildcard style/*.el)
--8<---------------cut here---------------end--------------->8---


> Strange enough, it doesn't catch the cl-member warning above and also
> not the ones Uwe mentioned

I see what Uwe reported when I run the regular make, with dynvars-check
I get the same results as you.

Best, Arash



reply via email to

[Prev in Thread] Current Thread [Next in Thread]