From: Eric Blake <eblake@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v1 1/2] Revert "build-sys: silence make by default or V=0"
Date: Tue, 23 Jan 2018 13:11:30 -0600 [thread overview]
Message-ID: <574ca3f0-b30e-a3de-b9ee-c49c756e30c1@redhat.com> (raw)
In-Reply-To: <20180123164718.12714-2-berrange@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1428 bytes --]
On 01/23/2018 10:47 AM, Daniel P. Berrange wrote:
> This reverts commit 42a77f1ce4934b243df003f95bda88530631387a.
>
> The primary intention of this change was to silence messages
> like
>
> make[1]: '/home/berrange/src/virt/qemu/capstone/libcapstone.a' is up to date.
>
> which we get when calling make recursively with explicit
> targets.
>
> The problem is that this change affected every make target,
> not merely the targets that triggered these "is up to date"
> messages. As a result any targets that were not invoking
> commands via "$(call quiet-command ...)" suddenly become
> silent. This is particularly bad for "make install" which
> now appears todo nothing.
>
> Rather than go through every make rule and try to identify
> places where we now need to explicitly print a message to
> show work taking place, just revert the change.
>
> To address the original problem of silencing "is up to date"
> messages, we simply add --quiet to the SUBDIR_MAKEVARS
> variable, so it only affects us on recursive make calls.
As for solving the original intended issue, this patch silences the
message about libcapstone, and reverting back to a known state is more
conservative, so I'm okay with this going in.
Tested-by: Eric Blake <eblake@redhat.com>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2018-01-23 19:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 16:47 [Qemu-devel] [PATCH v1 0/2] Two fixes to make rules Daniel P. Berrange
2018-01-23 16:47 ` [Qemu-devel] [PATCH v1 1/2] Revert "build-sys: silence make by default or V=0" Daniel P. Berrange
2018-01-23 17:02 ` Marc-Andre Lureau
2018-01-23 17:16 ` Mark Cave-Ayland
2018-01-23 19:11 ` Eric Blake [this message]
2018-01-23 16:47 ` [Qemu-devel] [PATCH v1 2/2] make: fix help message reference to bogus V=0 variable Daniel P. Berrange
2018-01-23 17:05 ` Marc-Andre Lureau
2018-01-23 19:05 ` Eric Blake
2018-01-24 10:17 ` Daniel P. Berrange
2018-02-07 14:56 ` [Qemu-devel] [PATCH v1 0/2] Two fixes to make rules 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=574ca3f0-b30e-a3de-b9ee-c49c756e30c1@redhat.com \
--to=eblake@redhat.com \
--cc=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@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).