From: Thomas Huth <thuth@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: meson incremental build doesn't handle config file going away
Date: Fri, 18 Feb 2022 13:08:24 +0100 [thread overview]
Message-ID: <fafc47f7-2801-92e3-61ca-fbdf407a8f92@redhat.com> (raw)
In-Reply-To: <CAFEAcA8nyOuQ_HziMVxgjFZYer9LUv-_QsKxzQY50By=6YUO=w@mail.gmail.com>
On 18/02/2022 12.59, Peter Maydell wrote:
> I've noticed that the meson incremental build doesn't seem to
> cleanly handle a config file going away, as ppc64abi32-linux-user
> has recently. The build fails with:
>
> ../../meson.build:1941:2: ERROR: Failed to load
> /mnt/nvmedisk/linaro/qemu-from-laptop/qemu/configs/targets/ppc64abi32-linux-user.mak:
> [Errno 2] No such file or directory:
> '/mnt/nvmedisk/linaro/qemu-from-laptop/qemu/configs/targets/ppc64abi32-linux-user.mak'
>
> where line 1941 is
> config_target += keyval.load('configs/targets' / target + '.mak')
>
> Rerunning make doesn't help; you have to manually re-run
> configure.
>
> Something here should figure out that "config file deleted" means
> it needs to rerun configure, I think.
That's weird, since the patch that removed that target actually change the
configure script, too, so it should have re-run configure afterwards... or
is that broken, too?
Thomas
next prev parent reply other threads:[~2022-02-18 12:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 11:59 meson incremental build doesn't handle config file going away Peter Maydell
2022-02-18 12:08 ` Thomas Huth [this message]
2022-02-18 12:12 ` Peter Maydell
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=fafc47f7-2801-92e3-61ca-fbdf407a8f92@redhat.com \
--to=thuth@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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).