From: Nigel Horne <njh@bandsman.co.uk>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Latest git doesn't compile
Date: Sat, 01 May 2010 12:25:35 -0400 [thread overview]
Message-ID: <4BDC55FF.5000404@bandsman.co.uk> (raw)
In-Reply-To: <1272721147.2723.3.camel@freedom>
On 05/01/2010 09:39 AM, Lucas Meneghel Rodrigues wrote:
> On Sat, 2010-05-01 at 09:29 -0400, Nigel Horne wrote:
>
>> ./configure --enable-linux-aio --enable-io-thread --enable-kvm
>> make clean
>> ...
>> gcc: block/blkdebug.o: No such file or directory
>>
>> -Nigel
>>
> A test job ran hours ago, and qemu.git compiled just fine here (check
> compile logs attached). Could you provide more info on what you do
> typically when compiling your tree? Have you tried with a clean git
> clone?
>
What further information would you like, when you ask for "more info"?
-Nigel
next prev parent reply other threads:[~2010-05-01 16:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201004301605.o3UG5E5e006653@bandsman.co.uk>
2010-05-01 13:29 ` [Qemu-devel] Latest git doesn't compile Nigel Horne
2010-05-01 13:39 ` Lucas Meneghel Rodrigues
2010-05-01 16:25 ` Nigel Horne [this message]
2010-05-03 12:10 ` Anthony Liguori
2010-05-04 2:48 ` Nigel Horne
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=4BDC55FF.5000404@bandsman.co.uk \
--to=njh@bandsman.co.uk \
--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).