unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: Lexical binding
Date: Sat, 2 Apr 2011 00:13:31 +0200	[thread overview]
Message-ID: <AANLkTikkW9-Bo9QyOvP1ZjbZHuMb-9iQGDv=qmwAJV_f@mail.gmail.com> (raw)
In-Reply-To: <83aag9ya87.fsf@gnu.org>

On Fri, Apr 1, 2011 at 22:42, Eli Zaretskii <eliz@gnu.org> wrote:

>  Compiling D:/gnu/bzr/emacs/trunk/lisp/files.el
>  In toplevel form:
>  D:/gnu/bzr/emacs/trunk/lisp/files.el:2242:1:Error: Lisp nesting exceeds `max-lisp-eval-depth'
>  Compiling D:/gnu/bzr/emacs/trunk/lisp/filesets.el
>  In toplevel form:
>  D:/gnu/bzr/emacs/trunk/lisp/filesets.el:1612:1:Error: Lisp nesting exceeds `max-lisp-eval-depth'
>  Compiling D:/gnu/bzr/emacs/trunk/lisp/startup.el
>  In toplevel form:
>  D:/gnu/bzr/emacs/trunk/lisp/startup.el:1295:1:Error: Lisp nesting exceeds `max-lisp-eval-depth'
>
> And later:
>
>  make[1]: *** No rule to make target `../lisp/files.elc', needed by `DOC'.  Stop.
[...]
> Does anyone else see this (on Windows or elsewhere)?

I have bootstrapped on Windows with no trouble at all (other than a
*lot* of new warnings) starting from a clean tree.

    Juanma



  reply	other threads:[~2011-04-01 22:13 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-01 17:32 Lexical binding Stefan Monnier
2011-04-01 19:12 ` David De La Harpe Golden
2011-04-01 19:46 ` Eli Zaretskii
2011-04-04 16:05   ` Stefan Monnier
2011-04-01 20:04 ` Daniel Colascione
2011-04-01 20:39 ` cedet-bzr build failure (was : Lexical binding) Darren Hoo
2011-04-01 21:21   ` David Engster
2011-04-01 22:26     ` Darren Hoo
2011-04-02 12:40       ` David Engster
2011-04-02 13:42         ` Eric M. Ludlam
2011-04-02 18:22           ` cedet-bzr build failure David Engster
2011-04-02 18:29         ` cedet-bzr build failure (was : Lexical binding) Darren Hoo
2011-04-01 20:42 ` Lexical binding Eli Zaretskii
2011-04-01 22:13   ` Juanma Barranquero [this message]
2011-04-02  2:33 ` Juanma Barranquero
2011-04-02  3:36   ` Juanma Barranquero
2011-04-02 18:38     ` Stefan Monnier
2011-04-04 16:04       ` Juanma Barranquero
2011-04-04 21:44         ` Stefan Monnier
2011-04-04 21:56           ` Juanma Barranquero
2011-04-04 22:03           ` David Kastrup
2011-04-04 22:34             ` Stefan Monnier
2011-04-02 18:38   ` Stefan Monnier
2011-04-02 18:50     ` Juanma Barranquero
2011-04-02 18:57       ` Juanma Barranquero
2011-04-03 12:05         ` Christian Ohler
2011-04-03 12:26           ` Juanma Barranquero
2011-04-03 23:32             ` Christian Ohler
2011-04-04  0:12               ` Juanma Barranquero
2011-04-04 16:22               ` Stefan Monnier

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='AANLkTikkW9-Bo9QyOvP1ZjbZHuMb-9iQGDv=qmwAJV_f@mail.gmail.com' \
    --to=lekktu@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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).