From: Stefan Weil <sw@weilnetz.de>
To: Kevin Wolf <kwolf@redhat.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Anthony Liguori" <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, "Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH v3] w32: Support tests (make check)
Date: Wed, 14 Mar 2012 18:14:02 +0100 [thread overview]
Message-ID: <4F60D1DA.9020206@weilnetz.de> (raw)
In-Reply-To: <4F609FA4.5020008@redhat.com>
Am 14.03.2012 14:39, schrieb Paolo Bonzini:
> Il 14/03/2012 10:10, Kevin Wolf ha scritto:
>> I have no idea if there's any chance of qemu-iotests successfully on
>> win32, but in order to make it actually run I think you would have to
>> change the file names in tests/qemu-iotests-quick.sh as well.
>
> I think the shell is able to add the suffix automatically, it's just
> make that needs it explicitly.
>
> Paolo
Yes, tests/qemu-iotests-quick.sh does not need a patch
to run the iotests on w32 or w64.
There are some other issues to solve for MinGW based
hosts:
* hostname does not support -s (is this option really needed?)
* there is no bc command (maybe the shell would be enough)
* TEST_DIR must not be an absolute path
* qemu-io does not read from stdin
* wrong order of arguments to qemu-io -c write, read
* other small issues
All these points can be fixed, and I already did run some of the tests.
The patch here only fixes make. Without it, make fails
with linker errors.
Regards,
Stefan W.
next prev parent reply other threads:[~2012-03-14 17:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 6:44 [Qemu-devel] [PATCH v3] w32: Support tests (make check) Stefan Weil
2012-03-14 9:10 ` Kevin Wolf
2012-03-14 13:39 ` Paolo Bonzini
2012-03-14 17:14 ` Stefan Weil [this message]
2012-03-14 13:35 ` Andreas Färber
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=4F60D1DA.9020206@weilnetz.de \
--to=sw@weilnetz.de \
--cc=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=kwolf@redhat.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).