qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-trivial] [PATCH 4/4] fix compilation when reconfiguring without dtrace backend
Date: Mon, 9 May 2011 10:06:52 +0100	[thread overview]
Message-ID: <BANLkTikrHj7SCHids+rvSb2Aw9TNinSNXg@mail.gmail.com> (raw)
In-Reply-To: <4DC7A8E0.1020500@redhat.com>

On Mon, May 9, 2011 at 9:42 AM, Paolo Bonzini <pbonzini@redhat.com> wrote:
> On 05/09/2011 10:34 AM, Stefan Hajnoczi wrote:
>> Is there some smart change detection you are thinking about or just
>> something like keeping the old copy of config-host.h and friends to
>> see if they have changed?
>
> Just that, perhaps for both .h and .mak files.  Consider this very patch; it
> is plausible that switching to another tracing backend does not change the
> .h files, right now the backend is only present in .h files to enable the
> monitor/cmdline interfaces.

Hmm...I was wrong when I said that just deleting .d files is enough.
If ./configure is run *and* an arbitrary header file was changed then
stale .o files will be used.  So we also need to delete .o files on
./configure.

Stefan

      reply	other threads:[~2011-05-09  9:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-02  7:54 [Qemu-devel] [PATCH 4/4] fix compilation when reconfiguring without dtrace backend Paolo Bonzini
2011-05-08 11:15 ` [Qemu-devel] [Qemu-trivial] " Stefan Hajnoczi
2011-05-09  6:53   ` Paolo Bonzini
2011-05-09  8:34     ` Stefan Hajnoczi
2011-05-09  8:42       ` Paolo Bonzini
2011-05-09  9:06         ` Stefan Hajnoczi [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=BANLkTikrHj7SCHids+rvSb2Aw9TNinSNXg@mail.gmail.com \
    --to=stefanha@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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).