From: Eric Blake <eblake@redhat.com>
To: Thomas Huth <thuth@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, "Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] configure: Remove old *-config-devices.mak.d files when running configure
Date: Mon, 11 Mar 2019 11:21:27 -0500 [thread overview]
Message-ID: <6d46de0f-a443-2c90-334b-edd34325ac16@redhat.com> (raw)
In-Reply-To: <1552300145-12526-1-git-send-email-thuth@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1603 bytes --]
On 3/11/19 5:29 AM, Thomas Huth wrote:
> When running "make" in a build directory from the pre-Kconfig merge time,
> the build process currently fails with:
>
> make: *** No rule to make target `.../default-configs/pci.mak',
> needed by `aarch64-softmmu/config-devices.mak'. Stop.
>
> To make sure that this problem at least goes away when the user runs
> "configure" (or "sh config.status") again, we have to make sure that
> we re-generate the .mak.d files. Thus remove the old stale files
> while running the configure script.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> configure | 3 +++
> 1 file changed, 3 insertions(+)
What are the conditions for make deciding it needs to rerun
config.status? Are end users still going to get 'make' failing with the
cryptic message (where we just advise on-list and on-wiki to
'./config.status' to fix it), or is there a way to build in a dependency
so that the makefile itself knows that if config.status has to be rerun,
that takes priority over any other rule that depends on .mak files?
>
> diff --git a/configure b/configure
> index b354e74..32c847f 100755
> --- a/configure
> +++ b/configure
> @@ -1792,6 +1792,9 @@ EOF
> exit 0
> fi
>
> +# Remove old dependency files to make sure that they get properly regenerated
> +rm -f *-config-devices.mak.d
> +
> if ! has $python; then
> error_exit "Python not found. Use --python=/path/to/python"
> fi
>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-03-11 16:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 10:29 [Qemu-devel] [PATCH] configure: Remove old *-config-devices.mak.d files when running configure Thomas Huth
2019-03-11 16:21 ` Eric Blake [this message]
2019-04-30 18:54 ` Thomas Huth
2019-04-30 18:54 ` Thomas Huth
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=6d46de0f-a443-2c90-334b-edd34325ac16@redhat.com \
--to=eblake@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--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).