From: Kazuhiro Ito <kzhr@d1.dion.ne.jp>
To: 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 20:16:42 +0900 [thread overview]
Message-ID: <20120614111657.0E2E52C803A@msa105.auone-net.jp> (raw)
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.
Please see the below patch.
=== modified file 'lisp/makefile.w32-in'
--- lisp/makefile.w32-in 2012-06-09 11:53:31 +0000
+++ lisp/makefile.w32-in 2012-06-14 00:18:51 +0000
@@ -396,7 +396,7 @@
# WARNING: Do NOT split the part inside $(ARGQUOTE)s into multiple lines as
# this can break with GNU Make 3.81 and later if sh.exe is used.
recompile: compile-first autoloads doit $(lisp)/progmodes/cc-mode.elc
- $(emacs) --eval $(ARGQUOTE)(batch-byte-recompile-directory 0)$(ARGQUOTE) $(lisp)
+ $(emacs) $(BYTE_COMPILE_FLAGS) --eval $(ARGQUOTE)(batch-byte-recompile-directory 0)$(ARGQUOTE) $(lisp)
$(lisp)/calendar/cal-loaddefs.el:
"$(EMACS)" $(EMACSOPT) -l autoload \
--
Kazuhiro Ito
next reply other threads:[~2012-06-14 11:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 11:16 Kazuhiro Ito [this message]
2012-06-14 16:27 ` bug#11707: 24.1.50; 'make recompile' does not use BYTE_COMPILE_FLAGS on Windows Eli Zaretskii
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
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=20120614111657.0E2E52C803A@msa105.auone-net.jp \
--to=kzhr@d1.dion.ne.jp \
--cc=11707@debbugs.gnu.org \
/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).