From: Juanma Barranquero <lekktu@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
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 19:41:56 +0200 [thread overview]
Message-ID: <CAAeL0SS1GL0-eK7ngLqQEa0RyPTcH-pxv6XgsegCoJHxZmfnLw@mail.gmail.com> (raw)
In-Reply-To: <jwvtx8kh7n7.fsf-monnier+emacsbugs@gnu.org>
On Tue, May 20, 2014 at 4:09 PM, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
>> 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?
No, I said "I just bootstrapped (or in fact, build at all) after two
weeks" because it was the first time in two weeks that I was able to
build, because of the pkg-config changes. revno:117116 magically
restored my ability to build. But it was a normal bootstrap.
> These macroexpansion failures should only be warnings, so do
> they prevent building Emacs?
No.
> If you can reproduce them, can you try to bump max-lisp-eval-depth a bit
> higher to see if it solves the problem?
I'll try and report back.
Thanks,
J
next prev parent reply other threads:[~2014-05-20 17:41 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
2014-05-20 17:41 ` Juanma Barranquero [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAeL0SS1GL0-eK7ngLqQEa0RyPTcH-pxv6XgsegCoJHxZmfnLw@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=17517@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).