all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 17517@debbugs.gnu.org
Subject: bug#17517: Eager macro-expansion failure: (error "Lisp nesting exceeds `max-lisp-eval-depth'")
Date: Tue, 20 May 2014 10:09:08 -0400	[thread overview]
Message-ID: <jwvtx8kh7n7.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <CAAeL0SSM2Ay6n6RQKLPQjirM1YYGKKkVh0ZRrbTGc3of-VW0Og@mail.gmail.com> (Juanma Barranquero's message of "Sat, 17 May 2014 10:15:48 +0200")

> I just bootstrapped (or in fact, build at all)

Not sure what this means.  Is this a "make bootstrap", or is it
something close yet different?

> Wrote c:/Devel/emacs/repo/trunk/lisp/calendar/cal-loaddefs.el
> Eager macro-expansion failure: (error "Lisp nesting exceeds
> `max-lisp-eval-depth'")

Of course, these may be due to simple "infinite recursion" problems
fixed by bootstrapping.  But they may also be due to "deep recursion",
in which case increasing max-lisp-eval-depth might help (IIRC I had to
bump this limit when I introduced eager macro-expansion, so it wouldn't
be a big surprise if it needs to be bumped yet a bit higher).

The eager macroexpansion can cause fairly deep recursion, especially
if/when some of the code (e.g. macroexp.el) is not yet byte-compiled.
It shouldn't be deeper than the macroexpansion done by the byte-compiler
(it's basically the exact same macroexpansion in both cases), but
because it happens earlier it's suffers more often of things like
"macroexp.el is not yet byte-compiled".

These macroexpansion failures should only be warnings, so do
they prevent building Emacs?

If you can reproduce them, can you try to bump max-lisp-eval-depth a bit
higher to see if it solves the problem?


        Stefan





  parent reply	other threads:[~2014-05-20 14:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-17  8:15 bug#17517: Eager macro-expansion failure: (error "Lisp nesting exceeds `max-lisp-eval-depth'") Juanma Barranquero
2014-05-19 15:40 ` Glenn Morris
2014-05-19 16:14   ` Juanma Barranquero
2014-05-19 16:22     ` Glenn Morris
2014-05-20 14:09 ` Stefan Monnier [this message]
2014-05-20 17:41   ` Juanma Barranquero
2014-12-14  5:53 ` Richard Copley
2015-04-06 15:59 ` bug#17517: Eager macro-expansion failure: (error "Lisp nesting, " Angelo Graziosi
2015-04-06 16:30   ` Eli Zaretskii
2015-04-06 19:56     ` Angelo Graziosi
2015-04-07  6:15       ` Eli Zaretskii
2015-04-08 12:16         ` Angelo Graziosi
2015-04-08 15:25           ` Eli Zaretskii

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=jwvtx8kh7n7.fsf-monnier+emacsbugs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=17517@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.