From: Paolo Bonzini <pbonzini@redhat.com>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Cc: Fam Zheng <famz@redhat.com>,
qemu-trivial@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
Eric Blake <eblake@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3] Makefile: Do not generate files if "configure" has not been run yet
Date: Thu, 8 Jun 2017 15:23:32 +0200 [thread overview]
Message-ID: <151f982c-8e35-5dba-e40c-5b1c5d76b6d1@redhat.com> (raw)
In-Reply-To: <1496926799-13040-1-git-send-email-thuth@redhat.com>
On 08/06/2017 14:59, Thomas Huth wrote:
> When doing a "make -j10" in the vanilla QEMU source tree (without
> running "configure" first), the Makefile currently generates two
> files already, qemu-version.h and qemu-options.def. This should not
> happen, so let's only build the generated files if config-host.mak
> is available (i.e. "configure" has been run already).
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> v3:
> - Check for config-host.mak at the place where we add the dependencies
> for $(GENERATED_FILES) instead of adding single dependencies all over
> the place
>
> Makefile | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Makefile b/Makefile
> index c830d7a..32d4441 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -791,9 +791,11 @@ endif # CONFIG_WIN
>
> # Add a dependency on the generated files, so that they are always
> # rebuilt before other object files
> +ifneq ($(wildcard config-host.mak),)
> ifneq ($(filter-out $(UNCHECKED_GOALS),$(MAKECMDGOALS)),$(if $(MAKECMDGOALS),,fail))
> Makefile: $(GENERATED_FILES)
> endif
> +endif
>
> .SECONDARY: $(TRACE_HEADERS) $(TRACE_HEADERS:%=%-timestamp) \
> $(TRACE_SOURCES) $(TRACE_SOURCES:%=%-timestamp) \
>
Thanks, queued.
Paolo
prev parent reply other threads:[~2017-06-08 13:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 12:59 [Qemu-devel] [PATCH v3] Makefile: Do not generate files if "configure" has not been run yet Thomas Huth
2017-06-08 13:23 ` Paolo Bonzini [this message]
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=151f982c-8e35-5dba-e40c-5b1c5d76b6d1@redhat.com \
--to=pbonzini@redhat.com \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=thuth@redhat.com \
/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).