qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Erik Rull <erik.rull@rdsoftware.de>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	qemu-devel@nongnu.org, Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] commit 67feec6ed854b3618b37ccf050b90192cbb96e0f breaks compilation of hw/pci.c
Date: Thu, 26 Jan 2012 15:58:00 +0100	[thread overview]
Message-ID: <4F2169F8.1030307@rdsoftware.de> (raw)
In-Reply-To: <4F212D34.5020004@suse.de>

Andreas Färber wrote:
> Am 26.01.2012 11:32, schrieb Jan Kiszka:
>> On 2012-01-26 11:00, Andreas Färber wrote:
>>> Am 26.01.2012 07:38, schrieb Gleb Natapov:
>>>> On Wed, Jan 25, 2012 at 10:07:14PM +0100, Erik Rull wrote:
>>>>> Is it possible that you provide this patch? Or was it already
>>>>> applied somewhere?
>>>>>
>>>> No patch needed. Just do "rm x86_64-softmmu/qmp-commands.h".
>>>
>>> Or for earlier versions "rm qmp-commands.h"; possibly also qapi-types.h
>>> and a third one.
>>>
>>> When in doubt, use a clean checkup and a dedicated build dir. Then you
>>> can just rm -rf *&&  ../qemu/configure&&  make -jx for each bisect step.
>>
>> make distclean also worked for me in those annoying cases.
>
> Usually yes. I recently had to submit
> dcfa486817c12ea41165265cfaaa236d11968626 to make that work (again?) for
> those files.
>
> Andreas
>

make distclean fixes that from my side. I was not aware of this option, I 
thought that make clean would be sufficient.

Thanks for pointing to that.

Best regards,

Erik

      reply	other threads:[~2012-01-26 14:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-25 11:22 [Qemu-devel] commit 67feec6ed854b3618b37ccf050b90192cbb96e0f breaks compilation of hw/pci.c erik.rull
2012-01-25 11:28 ` Gleb Natapov
2012-01-25 21:07   ` Erik Rull
2012-01-26  6:38     ` Gleb Natapov
2012-01-26 10:00       ` Andreas Färber
2012-01-26 10:32         ` Jan Kiszka
2012-01-26 10:38           ` Andreas Färber
2012-01-26 14:58             ` Erik Rull [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=4F2169F8.1030307@rdsoftware.de \
    --to=erik.rull@rdsoftware.de \
    --cc=afaerber@suse.de \
    --cc=gleb@redhat.com \
    --cc=jan.kiszka@siemens.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).