bug#17517: Eager macro-expansion failure: (error "Lisp nesting exceeds `max-lisp-eval-depth'")

bug#17517: Eager macro-expansion failure: (error "Lisp nesting exceeds `max-lisp-eval-depth'")

[Juanma Barranquero]

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 ...

bug#17517: Eager macro-expansion failure: (error "Lisp nesting exceeds `max-lisp-eval-depth'")

[Glenn Morris]

Other people don't seem to be seeing this.
Is this a make bootstrap?

bug#17517: Eager macro-expansion failure: (error "Lisp nesting exceeds `max-lisp-eval-depth'")

[Juanma Barranquero]

On Mon, May 19, 2014 at 5:40 PM, Glenn Morris <rgm@gnu.org> wrote:

> Other people don't seem to be seeing this.

Humm...

> Is this a make bootstrap?

Yes.

bug#17517: Eager macro-expansion failure: (error "Lisp nesting exceeds `max-lisp-eval-depth'")

[Glenn Morris]

Juanma Barranquero wrote:

>> Is this a make bootstrap?
>
> Yes.

Weird. Dunno then, sorry.

bug#17517: Eager macro-expansion failure: (error "Lisp nesting exceeds `max-lisp-eval-depth'")

[Stefan Monnier]

> 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

bug#17517: Eager macro-expansion failure: (error "Lisp nesting exceeds `max-lisp-eval-depth'")

[Juanma Barranquero]

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

bug#17517: Eager macro-expansion failure: (error "Lisp nesting exceeds `max-lisp-eval-depth'")

[Richard Copley]

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

bug#17517: Eager macro-expansion failure: (error "Lisp nesting, exceeds `max-lisp-eval-depth'")

[Angelo Graziosi]

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

bug#17517: Eager macro-expansion failure: (error "Lisp nesting, exceeds `max-lisp-eval-depth'")

[Eli Zaretskii]

> Date: Mon, 06 Apr 2015 17:59:50 +0200
> From: Angelo Graziosi <angelo.graziosi@alice.it>
> Cc: rcopley@gmail.com, Haroogan@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?

bug#17517: Eager macro-expansion failure: (error "Lisp nesting, exceeds `max-lisp-eval-depth'")

[Angelo Graziosi]

Il 06/04/2015 18:30, Eli Zaretskii ha scritto:
>> Date: Mon, 06 Apr 2015 17:59:50 +0200
>> From: Angelo Graziosi <angelo.graziosi@alice.it>
>> Cc: rcopley@gmail.com, Haroogan@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.

bug#17517: Eager macro-expansion failure: (error "Lisp nesting, exceeds `max-lisp-eval-depth'")

[Eli Zaretskii]

> Date: Mon, 06 Apr 2015 21:56:02 +0200
> From: Angelo Graziosi <angelo.graziosi@alice.it>
> CC: 17517@debbugs.gnu.org, rcopley@gmail.com, Haroogan@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@alice.it>
> >> Cc: rcopley@gmail.com, Haroogan@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.

bug#17517: Eager macro-expansion failure: (error "Lisp nesting, exceeds `max-lisp-eval-depth'")

[Angelo Graziosi]

Il 07/04/2015 08:15, Eli Zaretskii ha scritto:
>> Date: Mon, 06 Apr 2015 21:56:02 +0200
>> From: Angelo Graziosi <angelo.graziosi@alice.it>
>> CC: 17517@debbugs.gnu.org, rcopley@gmail.com, Haroogan@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@alice.it>
>>>> Cc: rcopley@gmail.com, Haroogan@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?

bug#17517: Eager macro-expansion failure: (error "Lisp nesting, exceeds `max-lisp-eval-depth'")

[Eli Zaretskii]

> Date: Wed, 08 Apr 2015 14:16:42 +0200
> From: Angelo Graziosi <angelo.graziosi@alice.it>
> CC: 17517@debbugs.gnu.org, rcopley@gmail.com, Haroogan@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@alice.it>
> >> CC: 17517@debbugs.gnu.org, rcopley@gmail.com, Haroogan@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@alice.it>
> >>>> Cc: rcopley@gmail.com, Haroogan@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.