From: Katsumi Yamaoka <yamaoka@jpl.org>
To: 19514@debbugs.gnu.org
Subject: bug#19514: 25.0.50; byte-compile-file too tight-lipped
Date: Mon, 05 Jan 2015 20:10:33 +0900 [thread overview]
Message-ID: <b4mppatiity.fsf@jpl.org> (raw)
Hi,
The byte compiler is now too quiet if it runs in the batch mode.
For instance, this is what I got when compiling Ma Gnus:
[...]
lispdir="/usr/local/share/emacs/25.0.50/site-lisp/gnus" srcdir=. emacs-25.0.50 -batch -q -no-site-file -l /usr/local/share/emacs/site-lisp/no-site-lisp.el -l ./dgnushack.el -f dgnushack-compile
No MH variant found on the system
Warning: Using brain-dead macro `mm-with-unibyte-current-buffer'!
Warning: Using brain-dead macro `mm-with-unibyte-current-buffer'!
Warning: Using brain-dead macro `mm-with-unibyte-current-buffer'!
Warning: Using brain-dead macro `mm-with-unibyte-current-buffer'!
Warning: Using brain-dead macro `mm-with-unibyte-current-buffer'!
Warning: Using brain-dead macro `mm-with-unibyte-current-buffer'!
Warning: Using brain-dead macro `mm-with-unibyte-current-buffer'!
Warning: Using brain-dead macro `mm-with-unibyte-current-buffer'!
Warning: Using brain-dead macro `mm-with-unibyte-current-buffer'!
Warning: Using brain-dead macro `mm-with-unibyte-current-buffer'!
Warning: Using brain-dead macro `mm-with-unibyte-current-buffer'!
Warning: Using brain-dead macro `mm-with-unibyte-current-buffer'!
Warning: Using brain-dead macro `mm-with-unibyte-current-buffer'!
Warning: Using brain-dead macro `mm-with-unibyte-current-buffer'!
[...]
I cannot see what Lisp modules are blamed. This seems to be due
to the recent change <cd2d58c1c81d608d6e1aefe1eb8a3d1f1cd60540>.
Thanks.
In GNU Emacs 25.0.50.1 (i686-pc-cygwin, GTK+ Version 3.10.9)
of 2015-01-05 on localhost
Windowing system distributor `The Cygwin/X Project', version 11.0.11501000
Configured using:
`configure --verbose --with-x-toolkit=gtk3'
next reply other threads:[~2015-01-05 11:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 11:10 Katsumi Yamaoka [this message]
2015-01-06 23:30 ` bug#19514: 25.0.50; byte-compile-file too tight-lipped Paul Eggert
2015-01-07 3:43 ` Katsumi Yamaoka
2015-01-07 7:04 ` Paul Eggert
2015-01-20 0:02 ` Katsumi Yamaoka
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=b4mppatiity.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=19514@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).