From: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, famz@redhat.com, mdroth@linux.vnet.ibm.com,
mitsuhiro.tanino@hds.com
Subject: [Qemu-devel] [PATCH 0/2] qga: vss-win32: Fix build failure
Date: Wed, 26 Mar 2014 14:28:38 -0400 [thread overview]
Message-ID: <20140326182838.11210.32245.stgit@hds.com> (raw)
Hello,
These patches are to fix recent build failures of qemu-guest-agent for
Windows when fsfreeze using VSS is enabled by:
./configure --cross-prefix=i686-w64-mingw32- --with-vss-sdk=yes
---
Tomoki Sekiyama (2):
Makefile: add qga-vss-dll-obj-y to nested variables
vss-win32: Fix build with mingw64-headers-3.1.0
Makefile | 1 +
qga/vss-win32/install.cpp | 3 +++
2 files changed, 4 insertions(+)
--
Tomoki Sekiyama
next reply other threads:[~2014-03-26 18:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 18:28 Tomoki Sekiyama [this message]
2014-03-26 18:28 ` [Qemu-devel] [PATCH 1/2] Makefile: add qga-vss-dll-obj-y to nested variables Tomoki Sekiyama
2014-03-26 18:28 ` [Qemu-devel] [PATCH 2/2] vss-win32: Fix build with mingw64-headers-3.1.0 Tomoki Sekiyama
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=20140326182838.11210.32245.stgit@hds.com \
--to=tomoki.sekiyama@hds.com \
--cc=famz@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mitsuhiro.tanino@hds.com \
--cc=pbonzini@redhat.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).