unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: David Engster <deng@randomsample.de>
To: Christopher Browne <cbbrowne@afilias.info>
Cc: 8764@debbugs.gnu.org
Subject: bug#8764: 24.0.50; cedet/semantic/bovine/c-by.el:184:1:Error: Lisp nesting exceeds `max-lisp-eval-depth'
Date: Mon, 30 May 2011 21:01:07 +0200	[thread overview]
Message-ID: <87r57gnhcc.fsf@engster.org> (raw)
In-Reply-To: <87ipssktyz.fsf@cbbrowne.afilias-int.info> (Christopher Browne's message of "Mon, 30 May 2011 12:56:36 -0400")

Christopher Browne writes:
> make[2]: Entering directory `/opt/emacs/trunk/lisp'
> Compiling cedet/semantic/bovine/c-by.el
>
> In toplevel form:
> cedet/semantic/bovine/c-by.el:184:1:Error: Lisp nesting exceeds `max-lisp-eval-depth'
> make[2]: *** [cedet/semantic/bovine/c-by.elc] Error 1
> make[2]: Leaving directory `/opt/emacs/trunk/lisp'
> make[1]: *** [compile-main] Error 2
> make[1]: Leaving directory `/opt/emacs/trunk/lisp'
> make: *** [lisp] Error 2
>
> At line 184, this file is defining the following object:
>
> (defconst semantic-c-by--parse-table
> ....
>
> I'm not sure where to proceed from here.  The default value is 600; I
> don't know if fiddling that higher would actually help.

It should. The build from CEDET-bzr uses a value of 1000 to compile the
resulting parser files. I'm actually a bit puzzled that this ever worked
reliably with the default value.

-David





  reply	other threads:[~2011-05-30 19:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-30 16:56 bug#8764: 24.0.50; cedet/semantic/bovine/c-by.el:184:1:Error: Lisp nesting exceeds `max-lisp-eval-depth' Christopher Browne
2011-05-30 19:01 ` David Engster [this message]
2011-05-30 22:14   ` Stefan Monnier
2011-05-30 22:50     ` Stefan Monnier
2011-05-30 19:04 ` Stefan Monnier
2011-05-30 19:19   ` Christopher Browne
2011-05-30 22:15     ` Stefan Monnier
2014-02-03 23:48       ` Lars Ingebrigtsen
2021-11-05 19:10 ` bug#8764: " Paul Eggert
2021-12-03 21:20   ` bug#8764: 24.0.50; " 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

  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=87r57gnhcc.fsf@engster.org \
    --to=deng@randomsample.de \
    --cc=8764@debbugs.gnu.org \
    --cc=cbbrowne@afilias.info \
    /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).