From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: 54816@debbugs.gnu.org
Cc: Alan Mackenzie <acm@muc.de>
Subject: bug#54816: 29.0.50; Silent "Compiler-macro error for cl-member" when building from scratch
Date: Sun, 10 Apr 2022 11:20:26 +0200 [thread overview]
Message-ID: <87r16570rp.fsf@gmail.com> (raw)
In-Reply-To: <877d7ypcu0.fsf@gmail.com> ("Kévin Le Gouguec"'s message of "Sat, 09 Apr 2022 16:10:15 +0200")
[-- Attachment #1: Type: text/plain, Size: 769 bytes --]
tags 54816 patch
thanks
Kévin Le Gouguec <kevin.legouguec@gmail.com> writes:
>> Compiler-macro error for cl-member: Handler: cl--compiler-macro-member
>> (excessive-variable-binding)
>> Eager macro-expansion failure: (excessive-variable-binding)
That bit about excessive-variable-binding rang a bell; I dimly
remembered seeing a couple of commits increasing max-specpdl-size "not
too long ago". git-log turned these up:
* 2022-01-31 "Enlarge max-specpdl-size for generation of files in
.../admin/grammars" (be2566eeab)
* 2022-01-30 "Enlarge max-specpdl-size for generation of leim-list.el in
bootstrap" (46611aa468)
So here's a "monkey see; monkey do" patch that causes this error to go
away; no idea if it's The Right Thing™ though?
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: max-specpdl-size.patch --]
[-- Type: text/x-patch, Size: 464 bytes --]
diff --git a/leim/Makefile.in b/leim/Makefile.in
index 6cf0abb40c..4e70e8b7e9 100644
--- a/leim/Makefile.in
+++ b/leim/Makefile.in
@@ -131,6 +131,7 @@ ${leimdir}/ja-dic/ja-dic.el:
${leimdir}/ja-dic/ja-dic.el: $(srcdir)/SKK-DIC/SKK-JISYO.L
$(AM_V_GEN)$(RUN_EMACS) -batch -l ja-dic-cnv \
+ --eval "(setq max-specpdl-size 5000)" \
-f batch-skkdic-convert -dir "$(leimdir)/ja-dic" "$<"
${srcdir}/../lisp/language/pinyin.el: ${srcdir}/MISC-DIC/pinyin.map
next prev parent reply other threads:[~2022-04-10 9:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-09 14:10 bug#54816: 29.0.50; Silent "Compiler-macro error for cl-member" when building from scratch Kévin Le Gouguec
2022-04-10 9:20 ` Kévin Le Gouguec [this message]
2022-04-10 12:43 ` Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r16570rp.fsf@gmail.com \
--to=kevin.legouguec@gmail.com \
--cc=54816@debbugs.gnu.org \
--cc=acm@muc.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.