From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] Change make to be quite again when doing nothing
Date: Wed, 14 Oct 2009 12:33:29 +0200 [thread overview]
Message-ID: <1255516409-19166-1-git-send-email-quintela@redhat.com> (raw)
Make don't print messages for sub-makes rules, but do it when targets are
files.
If you run make twice in a row, you get this:
$ make -j3
make[1]: `qemu-doc.html' is up to date.
make[1]: `qemu-tech.html' is up to date.
make[1]: `qemu.1' is up to date.
make[1]: `qemu-img.1' is up to date.
make[1]: `qemu-nbd.8' is up to date.
make[1]: `qemu-io' is up to date.
make[1]: `qemu-img' is up to date.
$
This patch removes this messages, and make is quiet again.
Idea for this patch cames for Paulo Bonzini.
Signed-off-by: Juan Quintela <quintela@redhat.com>
---
Makefile | 6 ++++--
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/Makefile b/Makefile
index 04e21bb..238bd84 100644
--- a/Makefile
+++ b/Makefile
@@ -20,7 +20,7 @@ Makefile: ;
configure: ;
.PHONY: all clean cscope distclean dvi html info install install-doc \
- recurse-all speed tar tarbin test build-all
+ recurse-all speed tar tarbin test build-all build-top-level
VPATH=$(SRC_PATH):$(SRC_PATH)/hw
@@ -41,7 +41,9 @@ config-all-devices.mak: $(SUBDIR_DEVICES_MAK)
-include config-all-devices.mak
build-all: config-host.h config-all-devices.h
- $(call quiet-command, $(MAKE) $(SUBDIR_MAKEFLAGS) $(TOOLS) $(DOCS) recurse-all,)
+ $(call quiet-command,$(MAKE) $(SUBDIR_MAKEFLAGS) V="$(V)" build-top-level recurse-all,)
+
+build-top-level: $(TOOLS) $(DOCS)
config-host.h: config-host.h-timestamp
config-host.h-timestamp: config-host.mak
--
1.6.2.5
next reply other threads:[~2009-10-14 10:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 10:33 Juan Quintela [this message]
2009-10-20 16:17 ` [Qemu-devel] [PATCH] Makefile: Change make to be quiet again when doing nothing Stefan Weil
2009-10-20 17:36 ` [Qemu-devel] " Paolo Bonzini
2009-10-21 21:17 ` Stefan Weil
2009-10-22 6:21 ` Paolo Bonzini
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=1255516409-19166-1-git-send-email-quintela@redhat.com \
--to=quintela@redhat.com \
--cc=qemu-devel@nongnu.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.
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 NNTP newsgroup(s).