GNU bug report logs -
#17517
Eager macro-expansion failure: (error "Lisp nesting exceeds `max-lisp-eval-depth'")
Previous Next
Reported by: Juanma Barranquero <lekktu <at> gmail.com>
Date: Sat, 17 May 2014 08:17:01 UTC
Severity: normal
Found in version 24.4.50
Done: Eli Zaretskii <eliz <at> gnu.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 17517 in the body.
You can then email your comments to 17517 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#17517
; Package
emacs
.
(Sat, 17 May 2014 08:17:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Juanma Barranquero <lekktu <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Sat, 17 May 2014 08:17:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Package: emacs
Version: 24.4.50
I just bootstrapped (or in fact, build at all) after two weeks and
suddenly I'm getting a lot of these:
Wrote c:/Devel/emacs/repo/trunk/lisp/calendar/cal-loaddefs.el
Eager macro-expansion failure: (error "Lisp nesting exceeds
`max-lisp-eval-depth'")
[...]
Eager macro-expansion failure: (error "Lisp nesting exceeds
`max-lisp-eval-depth'")
Generating autoloads for appt.el...
Wrote c:/Devel/emacs/repo/trunk/lisp/calendar/diary-loaddefs.el
Eager macro-expansion failure: (error "Lisp nesting exceeds
`max-lisp-eval-depth'")
[...]
Eager macro-expansion failure: (error "Lisp nesting exceeds
`max-lisp-eval-depth'")
Generating autoloads for appt.el...
Wrote c:/Devel/emacs/repo/trunk/lisp/calendar/hol-loaddefs.el
Eager macro-expansion failure: (error "Lisp nesting exceeds
`max-lisp-eval-depth'")
[...]
Eager macro-expansion failure: (error "Lisp nesting exceeds
`max-lisp-eval-depth'")
Generating autoloads for appt.el...
Wrote c:/Devel/emacs/repo/trunk/lisp/mh-e/mh-loaddefs.el
Eager macro-expansion failure: (error "Lisp nesting exceeds
`max-lisp-eval-depth'")
[...]
Eager macro-expansion failure: (error "Lisp nesting exceeds
`max-lisp-eval-depth'")
Generating autoloads for mh-acros.el...
Wrote c:/Devel/emacs/repo/trunk/lisp/net/tramp-loaddefs.el
Eager macro-expansion failure: (error "Lisp nesting exceeds
`max-lisp-eval-depth'")
[...]
Eager macro-expansion failure: (error "Lisp nesting exceeds
`max-lisp-eval-depth'")
Generating autoloads for ange-ftp.el...
Wrote c:/Devel/emacs/repo/trunk/lisp/loaddefs.el
Eager macro-expansion failure: (error "Lisp nesting exceeds
`max-lisp-eval-depth'")
[...]
Eager macro-expansion failure: (error "Lisp nesting exceeds
`max-lisp-eval-depth'")
Generating autoloads for align.el...
EMACSLOADPATH= '../src/bootstrap-emacs.exe' -batch --no-site-file
--no-site-lisp -l autoload \
--eval '(setq generate-autoload-cookie ";;;###obsolete-autoload")' \
--eval '(setq generated-autoload-file (expand-file-name
(unmsys--file-name "./loaddefs.el")))' \
-f batch-update-autoloads ./obsolete
Eager macro-expansion failure: (error "Lisp nesting exceeds
`max-lisp-eval-depth'")
[...]
Eager macro-expansion failure: (error "Lisp nesting exceeds
`max-lisp-eval-depth'")
Generating autoloads for obsolete/abbrevlist.el...
Saving file c:/Devel/emacs/repo/trunk/lisp/international/uni-name.el...
Eager macro-expansion failure: (error "Lisp nesting exceeds
`max-lisp-eval-depth'")
[...]
Eager macro-expansion failure: (error "Lisp nesting exceeds
`max-lisp-eval-depth'")
Wrote c:/Devel/emacs/repo/trunk/lisp/international/uni-name.el
Updating c:/Devel/emacs/repo/trunk/lisp/leim/leim-list.el ...
Eager macro-expansion failure: (error "Lisp nesting exceeds
`max-lisp-eval-depth'")
[...]
Eager macro-expansion failure: (error "Lisp nesting exceeds
`max-lisp-eval-depth'")
Checking c:/Devel/emacs/repo/trunk/lisp/leim/quail/ZOZY.el ...
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#17517
; Package
emacs
.
(Mon, 19 May 2014 15:41:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 17517 <at> debbugs.gnu.org (full text, mbox):
Other people don't seem to be seeing this.
Is this a make bootstrap?
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#17517
; Package
emacs
.
(Mon, 19 May 2014 16:16:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 17517 <at> debbugs.gnu.org (full text, mbox):
On Mon, May 19, 2014 at 5:40 PM, Glenn Morris <rgm <at> gnu.org> wrote:
> Other people don't seem to be seeing this.
Humm...
> Is this a make bootstrap?
Yes.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#17517
; Package
emacs
.
(Mon, 19 May 2014 16:23:01 GMT)
Full text and
rfc822 format available.
Message #14 received at 17517 <at> debbugs.gnu.org (full text, mbox):
Juanma Barranquero wrote:
>> Is this a make bootstrap?
>
> Yes.
Weird. Dunno then, sorry.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#17517
; Package
emacs
.
(Tue, 20 May 2014 14:10:01 GMT)
Full text and
rfc822 format available.
Message #17 received at 17517 <at> debbugs.gnu.org (full text, mbox):
> 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
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#17517
; Package
emacs
.
(Tue, 20 May 2014 17:43:02 GMT)
Full text and
rfc822 format available.
Message #20 received at 17517 <at> debbugs.gnu.org (full text, mbox):
On Tue, May 20, 2014 at 4:09 PM, Stefan Monnier
<monnier <at> 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
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#17517
; Package
emacs
.
(Sun, 14 Dec 2014 05:54:02 GMT)
Full text and
rfc822 format available.
Message #23 received at 17517 <at> debbugs.gnu.org (full text, mbox):
I experimented with different settings of max-lisp-eval-depth. I just
changed the default directly in "init_eval_once" in eval.c and
bootstrapped.
With the current value 600 there are hundreds of these warnings.
With 750 there are a few dozen.
With 800 there are none.
In GNU Emacs 25.0.50.1 (x86_64-w64-mingw32)
of 2014-12-12 on MACHINE
Repository revision: 074965f9355b7cc7f7a5f4385a19433e51c8afd2
Windowing system distributor `Microsoft Corp.', version 6.3.9600
Configured using:
`configure --prefix /c/emacs/emacs-20141212-145542
--disable-dependency-tracking
--enable-locallisppath=%emacs_dir%/../site-lisp --with-wide-int
--build=x86_64-w64-mingw32 'CPPFLAGS=-I G:/usr/include -I
C:/GnuWin32/include -march=native -mtune=native' 'LDFLAGS=-L G:/usr/lib
-L C:/GnuWin32/lib''
Configured features:
XPM JPEG TIFF GIF PNG SOUND NOTIFY ACL GNUTLS LIBXML2 ZLIB
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#17517
; Package
emacs
.
(Mon, 06 Apr 2015 16:01:02 GMT)
Full text and
rfc822 format available.
Message #26 received at 17517 <at> debbugs.gnu.org (full text, mbox):
I see these failures building current Emacs-git master on MSYS2-MINGW64,
but if I remove the .git directory from the git cloned tree (*), the
failures are absent.
Ciao,
Angelo.
----
(*) the tree is cloned with the command:
git clone -b master git://git.sv.gnu.org/emacs.git
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#17517
; Package
emacs
.
(Mon, 06 Apr 2015 16:31:02 GMT)
Full text and
rfc822 format available.
Message #29 received at 17517 <at> debbugs.gnu.org (full text, mbox):
> Date: Mon, 06 Apr 2015 17:59:50 +0200
> From: Angelo Graziosi <angelo.graziosi <at> alice.it>
> Cc: rcopley <at> gmail.com, Haroogan <at> gmail.com
>
> I see these failures building current Emacs-git master on MSYS2-MINGW64,
> but if I remove the .git directory from the git cloned tree (*), the
> failures are absent.
Do the problems go away if you enlarge the value of
max-lisp-eval-depth passed to Emacs during the build?
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#17517
; Package
emacs
.
(Mon, 06 Apr 2015 19:57:02 GMT)
Full text and
rfc822 format available.
Message #32 received at 17517 <at> debbugs.gnu.org (full text, mbox):
Il 06/04/2015 18:30, Eli Zaretskii ha scritto:
>> Date: Mon, 06 Apr 2015 17:59:50 +0200
>> From: Angelo Graziosi <angelo.graziosi <at> alice.it>
>> Cc: rcopley <at> gmail.com, Haroogan <at> gmail.com
>>
>> I see these failures building current Emacs-git master on MSYS2-MINGW64,
>> but if I remove the .git directory from the git cloned tree (*), the
>> failures are absent.
>
> Do the problems go away if you enlarge the value of
> max-lisp-eval-depth passed to Emacs during the build?
>
I have tried the same value suggested in
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=17517 (message #23), i.e.
max_lisp_eval_depth = 800
and the failures are removed.
Ciao,
Angelo.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#17517
; Package
emacs
.
(Tue, 07 Apr 2015 06:16:01 GMT)
Full text and
rfc822 format available.
Message #35 received at 17517 <at> debbugs.gnu.org (full text, mbox):
> Date: Mon, 06 Apr 2015 21:56:02 +0200
> From: Angelo Graziosi <angelo.graziosi <at> alice.it>
> CC: 17517 <at> debbugs.gnu.org, rcopley <at> gmail.com, Haroogan <at> gmail.com
>
> Il 06/04/2015 18:30, Eli Zaretskii ha scritto:
> >> Date: Mon, 06 Apr 2015 17:59:50 +0200
> >> From: Angelo Graziosi <angelo.graziosi <at> alice.it>
> >> Cc: rcopley <at> gmail.com, Haroogan <at> gmail.com
> >>
> >> I see these failures building current Emacs-git master on MSYS2-MINGW64,
> >> but if I remove the .git directory from the git cloned tree (*), the
> >> failures are absent.
> >
> > Do the problems go away if you enlarge the value of
> > max-lisp-eval-depth passed to Emacs during the build?
> >
>
> I have tried the same value suggested in
> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=17517 (message #23), i.e.
>
> max_lisp_eval_depth = 800
>
> and the failures are removed.
So perhaps it's time for enlarging that value.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#17517
; Package
emacs
.
(Wed, 08 Apr 2015 12:17:01 GMT)
Full text and
rfc822 format available.
Message #38 received at 17517 <at> debbugs.gnu.org (full text, mbox):
Il 07/04/2015 08:15, Eli Zaretskii ha scritto:
>> Date: Mon, 06 Apr 2015 21:56:02 +0200
>> From: Angelo Graziosi <angelo.graziosi <at> alice.it>
>> CC: 17517 <at> debbugs.gnu.org, rcopley <at> gmail.com, Haroogan <at> gmail.com
>>
>> Il 06/04/2015 18:30, Eli Zaretskii ha scritto:
>>>> Date: Mon, 06 Apr 2015 17:59:50 +0200
>>>> From: Angelo Graziosi <angelo.graziosi <at> alice.it>
>>>> Cc: rcopley <at> gmail.com, Haroogan <at> gmail.com
>>>>
>>>> I see these failures building current Emacs-git master on MSYS2-MINGW64,
>>>> but if I remove the .git directory from the git cloned tree (*), the
>>>> failures are absent.
>>>
>>> Do the problems go away if you enlarge the value of
>>> max-lisp-eval-depth passed to Emacs during the build?
>>>
>>
>> I have tried the same value suggested in
>> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=17517 (message #23), i.e.
>>
>> max_lisp_eval_depth = 800
>>
>> and the failures are removed.
>
> So perhaps it's time for enlarging that value.
>
Who should do that?
Reply sent
to
Eli Zaretskii <eliz <at> gnu.org>
:
You have taken responsibility.
(Wed, 08 Apr 2015 15:26:03 GMT)
Full text and
rfc822 format available.
Notification sent
to
Juanma Barranquero <lekktu <at> gmail.com>
:
bug acknowledged by developer.
(Wed, 08 Apr 2015 15:26:03 GMT)
Full text and
rfc822 format available.
Message #43 received at 17517-done <at> debbugs.gnu.org (full text, mbox):
> Date: Wed, 08 Apr 2015 14:16:42 +0200
> From: Angelo Graziosi <angelo.graziosi <at> alice.it>
> CC: 17517 <at> debbugs.gnu.org, rcopley <at> gmail.com, Haroogan <at> gmail.com
>
>
> Il 07/04/2015 08:15, Eli Zaretskii ha scritto:
> >> Date: Mon, 06 Apr 2015 21:56:02 +0200
> >> From: Angelo Graziosi <angelo.graziosi <at> alice.it>
> >> CC: 17517 <at> debbugs.gnu.org, rcopley <at> gmail.com, Haroogan <at> gmail.com
> >>
> >> Il 06/04/2015 18:30, Eli Zaretskii ha scritto:
> >>>> Date: Mon, 06 Apr 2015 17:59:50 +0200
> >>>> From: Angelo Graziosi <angelo.graziosi <at> alice.it>
> >>>> Cc: rcopley <at> gmail.com, Haroogan <at> gmail.com
> >>>>
> >>>> I see these failures building current Emacs-git master on MSYS2-MINGW64,
> >>>> but if I remove the .git directory from the git cloned tree (*), the
> >>>> failures are absent.
> >>>
> >>> Do the problems go away if you enlarge the value of
> >>> max-lisp-eval-depth passed to Emacs during the build?
> >>>
> >>
> >> I have tried the same value suggested in
> >> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=17517 (message #23), i.e.
> >>
> >> max_lisp_eval_depth = 800
> >>
> >> and the failures are removed.
> >
> > So perhaps it's time for enlarging that value.
> >
>
> Who should do that?
Somebody.
Done.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Thu, 07 May 2015 11:24:05 GMT)
Full text and
rfc822 format available.
This bug report was last modified 10 years and 46 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.