From: Brad Smith <brad@comstyle.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] More build breakage: signrom.sh vs kvmvapic.bin
Date: Sun, 01 Apr 2012 04:55:23 -0400 [thread overview]
Message-ID: <4F7817FB.8040702@comstyle.com> (raw)
In-Reply-To: <4F7813AB.5000802@web.de>
On 01/04/12 4:36 AM, Jan Kiszka wrote:
> It is only build on x86 unix hosts minus Mac. We are shipping it as
> binary for the rest. There is WIP on getting KVM working for Solaris, so
> this may not be of Linux-only interest in the future.
Ok so you then build it on Linux and Solaris. But I don't see the point of
building it on any OS that does not have KVM since you'll never use it
there.
> signrom.sh is horribly slow and should be replaced soon, see
> http://thread.gmane.org/gmane.comp.emulators.qemu/139368
I don't care if it's slow. The build is broken. That is what matters.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
prev parent reply other threads:[~2012-04-01 8:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-01 2:48 [Qemu-devel] More build breakage: signrom.sh vs kvmvapic.bin Brad Smith
2012-04-01 8:36 ` Jan Kiszka
2012-04-01 8:39 ` Jan Kiszka
2012-04-01 8:55 ` Brad Smith [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=4F7817FB.8040702@comstyle.com \
--to=brad@comstyle.com \
--cc=aliguori@us.ibm.com \
--cc=jan.kiszka@web.de \
--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).