unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: acm@muc.de, Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Make the compilation slightly less verbose?
Date: Sat, 15 Jun 2019 16:25:31 +0200	[thread overview]
Message-ID: <87y3237wo4.fsf@igel.home> (raw)
In-Reply-To: <m3sgsb9dto.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 15 Jun 2019 15:29:39 +0200")

On Jun 15 2019, Lars Ingebrigtsen <larsi@gnus.org> wrote:

> Eli Zaretskii <eliz@gnu.org> writes:
>
>> Please make the change be conditioned on the verbosity, i.e. I'd very
>> much like it if "make V=1" would still emit these messages.
>
> I seem to have almost completely successfully managed to suppress all my
> knowledge I may once have had of how autoconf works, but...  Does this
> look right?
>
> diff --git a/src/Makefile.in b/src/Makefile.in
> index be769458d3..b89a2f890e 100644
> --- a/src/Makefile.in
> +++ b/src/Makefile.in
> @@ -776,7 +776,12 @@ .PHONY:
>  ## bootstrap-emacs$(EXEEXT) as an order-only prerequisite.
>  
>  %.elc: %.el | bootstrap-emacs$(EXEEXT) $(bootstrap_pdmp)
> +ifeq (@AM_V@,)
> +	@$(MAKE) --no-print-directory\
> +		-C ../lisp EMACS="$(bootstrap_exe)" THEFILE=$< $<c
> +else
>  	@$(MAKE) -C ../lisp EMACS="$(bootstrap_exe)" THEFILE=$< $<c
> +endif

AM_V_NO_PD = $(am__v_NO_PD_@AM_V@)
am__v_NO_PD_ = $(am__v_NO_PD_@AM_DEFAULT_V@)
am__v_NO_PD_0 = --no-print-directory
am__v_NO_PD_1 =

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."



  parent reply	other threads:[~2019-06-15 14:25 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
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 [this message]
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

  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=87y3237wo4.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=acm@muc.de \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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).