all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Kazuhiro Ito <kzhr@d1.dion.ne.jp>
Cc: 11707@debbugs.gnu.org
Subject: bug#11707: 24.1.50; 'make recompile' does not use BYTE_COMPILE_FLAGS on Windows
Date: Thu, 14 Jun 2012 19:27:26 +0300	[thread overview]
Message-ID: <83haudyi35.fsf@gnu.org> (raw)
In-Reply-To: <20120614111657.0E2E52C803A@msa105.auone-net.jp>

> Date: Thu, 14 Jun 2012 20:16:42 +0900
> From: Kazuhiro Ito <kzhr@d1.dion.ne.jp>
> 
> When I 'make recompile' on Windows, Emacs outputs many "Lisp nesting
> exceeds `max-lisp-eval-depth'" message.
> 
> The cause of the problem is that lisp/makefile.w32-in does not use
> BYTE_COMPILE_FLAGS variable when recompile.  On the other hand,
> lisp/Makefile.in use it.

lisp/makefile.w32-in doesn't use BYTE_COMPILE_FLAGS because they are
not supposed to be needed for that target.

Are you using "make recompile" with emacs.exe that has only source
(*.el) version of the byte compiler loaded?  Otherwise, I don't
understand how come you get these errors.

I don't want to blindly enlarge the stack of the byte compiler without
understanding the problem which causes the errors.





  reply	other threads:[~2012-06-14 16:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14 11:16 bug#11707: 24.1.50; 'make recompile' does not use BYTE_COMPILE_FLAGS on Windows Kazuhiro Ito
2012-06-14 16:27 ` Eli Zaretskii [this message]
2012-06-15 16:41   ` Kazuhiro Ito
2012-06-15 17:41     ` Eli Zaretskii
2012-06-18 12:56       ` Kazuhiro Ito
2012-06-25  1:10       ` Glenn Morris
2012-06-25 11:35         ` Juanma Barranquero
2012-06-26 16:28           ` Glenn Morris
2012-06-26 17:08             ` Eli Zaretskii
2012-06-28 17:30               ` Glenn Morris
2012-06-28 18:15                 ` Eli Zaretskii
2012-06-25 14:35         ` Stefan Monnier
2012-06-28 17:34           ` Glenn Morris
2012-06-28 18:11             ` Stefan Monnier
2012-07-06  7:44           ` Glenn Morris
2013-12-18 21:40             ` Glenn Morris

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83haudyi35.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=11707@debbugs.gnu.org \
    --cc=kzhr@d1.dion.ne.jp \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.