From: Stefan Weil <weil@mail.berlios.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] configure: Disable guest_agent for mingw32
Date: Sun, 07 Aug 2011 18:41:50 +0200 [thread overview]
Message-ID: <4E3EC04E.60606@mail.berlios.de> (raw)
In-Reply-To: <4E3EB457.6060202@codemonkey.ws>
Am 07.08.2011 17:50, schrieb Anthony Liguori:
> On 08/06/2011 03:47 PM, Stefan Weil wrote:
>> guest_agent is not supported for mingw32, so the default value
>> should be 'no', not 'yes'.
>
> Why is it not supported? It should build just fine.
>
> If the answer is, -mms-bitfield, then we should fix slirp instead of
> disabling guest-agent.
>
> Regards,
>
> Anthony Liguori
Code extract from configure:
if [ "$linux" = "yes" -o "$bsd" = "yes" -o "$solaris" = "yes" ] ; then
tools="qemu-nbd\$(EXESUF) $tools"
if [ "$guest_agent" = "yes" ]; then
tools="qemu-ga\$(EXESUF) $tools"
fi
if [ "$check_utests" = "yes" ]; then
tools="check-qint check-qstring check-qdict check-qlist $tools"
tools="check-qfloat check-qjson $tools"
fi
fi
MinGW32 is neither linux nor bsd nor solaris, so guest_agent="yes"
won't enable qemu-ga.exe.
Of course this (and the bitfield related problems) should be fixed in
git master, but not in stable-0.15. So for 0.15, the patch is a must
(unless you are prepared to take additional patches for the
bitfield issues).
Even for git master, the patch is reasonable because it allows
QEMU builds with most mingw32 installations. As soon as
there is a w32 QEMU working with glib-2.0 and a w32 qemu-ga.exe
(and some documentation in the QEMU wiki how to get glib-2.0
and python), the patch can be reverted.
Regards,
Stefan Weil
next prev parent reply other threads:[~2011-08-07 16:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-06 20:47 [Qemu-devel] [PATCH] configure: Disable guest_agent for mingw32 Stefan Weil
2011-08-07 10:25 ` Stefan Weil
2011-08-07 15:50 ` Anthony Liguori
2011-08-07 16:41 ` Stefan Weil [this message]
2011-08-08 19:17 ` Anthony Liguori
2011-08-12 13:47 ` Anthony Liguori
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=4E3EC04E.60606@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=anthony@codemonkey.ws \
--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).