From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 36216@debbugs.gnu.org
Subject: bug#36216: 27.0.50; Variable binding depth exceeds max-specpld-size during bootstrap
Date: Sun, 16 Jun 2019 17:04:38 +0300 [thread overview]
Message-ID: <83k1dlvd6x.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0SRMPWvOqg6ep=+f6YnyJGY3iUF6UPb0LCC51eAQ3SfGZA@mail.gmail.com> (message from Juanma Barranquero on Sun, 16 Jun 2019 14:01:22 +0200)
> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Sun, 16 Jun 2019 14:01:22 +0200
> Cc: 36216@debbugs.gnu.org
>
> diff --git i/lisp/loadup.el w/lisp/loadup.el
> index 67e8aa7d40..ca0babd6ed 100644
> --- i/lisp/loadup.el
> +++ w/lisp/loadup.el
> @@ -105,4 +105,8 @@
> ;; We'll probably overflow the pure space.
> (setq purify-flag nil)
> + ;; Set max-specpdl-size to a larger value to avoid a
> + ;; macroexpansion error when loading the cl-generic.el
> + ;; source file (bug#36216).
> + (setq max-specpdl-size 1450)
> ;; Value of max-lisp-eval-depth when compiling initially.
>
> ;; During bootstrapping the byte-compiler is run interpreted
Since you've established that the problem is not infinite recursion,
any such solution is OK. But maybe we simply should bump the default
value of that variable?
next prev parent reply other threads:[~2019-06-16 14:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-15 0:53 bug#36216: 27.0.50; Variable binding depth exceeds max-specpld-size during bootstrap Juanma Barranquero
2019-06-15 6:29 ` Eli Zaretskii
2019-06-15 10:00 ` Juanma Barranquero
2019-06-15 10:13 ` Eli Zaretskii
2019-06-16 5:57 ` Juanma Barranquero
2019-06-16 12:01 ` Juanma Barranquero
2019-06-16 14:04 ` Eli Zaretskii [this message]
2019-06-16 14:17 ` Juanma Barranquero
2019-06-16 14:20 ` Eli Zaretskii
2019-06-16 19:34 ` Stefan Monnier
2019-06-16 19:49 ` Juanma Barranquero
2019-06-16 21:22 ` Juanma Barranquero
2019-06-27 20:17 ` Juanma Barranquero
2019-06-16 21:32 ` Stefan Monnier
2019-06-15 11:22 ` Lars Ingebrigtsen
2019-06-16 6:01 ` Juanma Barranquero
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=83k1dlvd6x.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=36216@debbugs.gnu.org \
--cc=lekktu@gmail.com \
/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.