From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
schwab@linux-m68k.org, emacs-devel@gnu.org
Subject: Re: Make the compilation slightly less verbose?
Date: Fri, 14 Jun 2019 19:28:49 +0000 [thread overview]
Message-ID: <20190614192849.GC23182@ACM> (raw)
In-Reply-To: <83y324vvsz.fsf@gnu.org>
Hello, Eli.
On Fri, Jun 14, 2019 at 21:58:04 +0300, Eli Zaretskii wrote:
> > From: Lars Ingebrigtsen <larsi@gnus.org>
> > Date: Fri, 14 Jun 2019 18:10:22 +0200
> > Cc: emacs-devel@gnu.org
> > diff --git a/src/Makefile.in b/src/Makefile.in
> > index be769458d3..5fc623c346 100644
> > --- a/src/Makefile.in
> > +++ b/src/Makefile.in
> > @@ -776,7 +776,8 @@ .PHONY:
> > ## bootstrap-emacs$(EXEEXT) as an order-only prerequisite.
> > %.elc: %.el | bootstrap-emacs$(EXEEXT) $(bootstrap_pdmp)
> > - @$(MAKE) -C ../lisp EMACS="$(bootstrap_exe)" THEFILE=$< $<c
> > + @$(MAKE) --no-print-directory \
> > + -C ../lisp EMACS="$(bootstrap_exe)" THEFILE=$< $<c
> > ## VCSWITNESS points to the file that holds info about the current checkout.
> > ## We use it as a heuristic to decide when to rebuild loaddefs.el.
> > I now get
> > ELC ../lisp/dos-fns.elc
> > ELC ../lisp/dos-vars.elc
> > ELC ../lisp/dos-w32.elc
> > ELC ../lisp/dynamic-setting.elc
> > on a make bootstrap, and otherwise things look the same as before, I
> > think.
> > Does anybody object to this change?
> I don't really see why your personal preferences should be forced on
> all of us.
Well, somebody's personal preference must prevail, unless we introduce a
new configuration option (PLEASE NOT!).
If I understand this correctly, three lines of output were being output
for each file, and the information content of two of these was close to,
if not actually, zero.
So I see this as an objectively desirable change.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2019-06-14 19:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 15:27 Make the compilation slightly less verbose? Lars Ingebrigtsen
2019-06-14 15:56 ` Andreas Schwab
2019-06-14 16:10 ` Lars Ingebrigtsen
2019-06-14 18:58 ` Eli Zaretskii
2019-06-14 19:28 ` Alan Mackenzie [this message]
2019-06-14 20:12 ` Werner LEMBERG
2019-06-15 6:00 ` Eli Zaretskii
2019-06-15 7:54 ` Eli Zaretskii
2019-06-15 10:58 ` Stefan Monnier
2019-06-15 13:29 ` Lars Ingebrigtsen
2019-06-15 13:53 ` Eli Zaretskii
2019-06-15 13:55 ` Lars Ingebrigtsen
2019-06-15 14:16 ` Eli Zaretskii
2019-06-15 14:21 ` Lars Ingebrigtsen
2019-06-15 14:25 ` Andreas Schwab
2019-06-16 22:32 ` Lars Ingebrigtsen
2019-06-14 19:35 ` Óscar Fuentes
2019-06-14 20:14 ` Stefan Monnier
2019-06-15 0:50 ` Paul Eggert
2019-06-14 20:13 ` David Ringo
2019-06-15 13:30 ` Lars Ingebrigtsen
2019-06-14 16:10 ` Eli Zaretskii
2019-06-14 17:24 ` Andy Moreton
2019-06-15 13:32 ` Lars Ingebrigtsen
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=20190614192849.GC23182@ACM \
--to=acm@muc.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=schwab@linux-m68k.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 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.