From: Thomas Mueller <thomas@chaschperli.ch>
To: kvm@vger.kernel.org
Subject: Re: [ANNOUNCE] qemu-kvm-0.11.0-rc1
Date: Thu, 6 Aug 2009 09:31:48 +0000 (UTC) [thread overview]
Message-ID: <h5e7u4$ehh$1@ger.gmane.org> (raw)
In-Reply-To: 4A75BF82.60005@redhat.com
On Sun, 02 Aug 2009 19:32:02 +0300, Avi Kivity wrote:
> Paralleling the qemu upstream 0.11 release cycle, qemu-kvm-0.11.0-rc1 is
> now available. qemu-kvm-0.11.0-rc1 can be used with kvm kernel modules
> from your distribution kernel, or with the modules provided by the
> kvm-kmod package.
>
> Please test it out and report bugs, so we can have a stable
> qemu-kvm-0.10.0 release.
"make clean" fails if not done a "./configure" before. the debian build
process first does a "make clean" before doing anything - so it fails
building the package because of this.
debian:/tmp/qemu-kvm-0.11.0-rc1# make clean
rm -f config.mak config.h op-i386.h opc-i386.h gen-op-i386.h op-arm.h opc-
arm.h gen-op-arm.h
rm -f *.o *.d *.a TAGS cscope.* *.pod *~ */*~
rm -f slirp/*.o slirp/*.d audio/*.o audio/*.d block/*.o block/*.d
rm -f qemu-img-cmds.h
make -C tests clean
make[1]: Entering directory `/tmp/qemu-kvm-0.11.0-rc1/tests'
rm -f *~ *.o test-i386.out test-i386.ref \
test-x86_64.log test-x86_64.ref qruncom sha1
make[1]: Leaving directory `/tmp/qemu-kvm-0.11.0-rc1/tests'
for d in libhw32 libhw64; do \
make -C $d clean || exit 1 ; \
done
make: *** libhw32: No such file or directory. Stop.
make: *** [clean] Error 1
- Thomas
next prev parent reply other threads:[~2009-08-06 9:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-02 16:32 [ANNOUNCE] qemu-kvm-0.11.0-rc1 Avi Kivity
2009-08-06 9:31 ` Thomas Mueller [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-07 13:05 Avi Kivity
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='h5e7u4$ehh$1@ger.gmane.org' \
--to=thomas@chaschperli.ch \
--cc=kvm@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.