From: Paul Eggert <eggert@cs.ucla.edu>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 8764@debbugs.gnu.org, Christopher Browne <cbbrowne@afilias.info>,
David Engster <deng@randomsample.de>
Subject: bug#8764: cedet/semantic/bovine/c-by.el:184:1:Error: Lisp nesting exceeds `max-lisp-eval-depth'
Date: Fri, 5 Nov 2021 12:10:39 -0700 [thread overview]
Message-ID: <2ec9475a-fdd6-3325-b9f1-9cd7b1df6e5f@cs.ucla.edu> (raw)
In-Reply-To: <87ipssktyz.fsf@cbbrowne.afilias-int.info>
> it would be worthwhile to
> try and figure out what is different between your case and the
> bootstrap case.
I ran into this problem recently on Emacs master (commit
133026c362eb27191d992fbf35727550804bfc96 dated today). I had recently
done a 'git pull' into a working directory that hadn't been updated for
some time. When I did the usual './autogen.sh; ./configure; make' I got
the same diagnostic for c-by.el.
The problem persisted after I removed all *.elc files and then did a
'make -j5' on a 4-core machine. The problem then went away when I did a
plain 'make'.
One hypothesis is that c-by.el depends on some other .el file being
compiled into *.elc form (rather than being present in only source
form), and that using 'make -j5' causes 'make' on my platform to
(unluckily) arrange for c-by.el to be compiled before the other *.elc
file (whatever it is) is available.
c-by.el starts this way:
(require 'semantic/lex)
(eval-when-compile (require 'semantic/bovine))
so perhaps we should arrange for all the .elc files needed by
semantic/lex and/or semantic/bovine to be present, before compiling c-by.el.
next prev parent reply other threads:[~2021-11-05 19:10 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
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 ` Paul Eggert [this message]
2021-12-03 21:20 ` 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=2ec9475a-fdd6-3325-b9f1-9cd7b1df6e5f@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=8764@debbugs.gnu.org \
--cc=cbbrowne@afilias.info \
--cc=deng@randomsample.de \
--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).