From: Paolo Bonzini <pbonzini@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Stefan Weil <sw@weilnetz.de>,
qemu-devel@nongnu.org,
Alexander Voropay <alexander.voropay@gmail.com>
Subject: Re: [Qemu-devel] qemu-1.6.0 under Cygwin64 ./configure failed
Date: Tue, 24 Sep 2013 17:40:19 +0200 [thread overview]
Message-ID: <5241B263.8060105@redhat.com> (raw)
In-Reply-To: <5241A49A.3080509@redhat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Il 24/09/2013 16:41, Eric Blake ha scritto:
> -mno-cygwin is an obsolete command line option, formerly used for
> cross-compiling from cygwin to mingw. It is NOT used when building
> for cygwin, and these days, building for mingw should use a proper
> cross compiler (available from cygwin.com) rather than the
> -mno-cygwin crutch. To me, this means that there is some cruft in
> the configure file, and that no one has ever really tried to port
> qemu to cygwin yet.
Yes, QEMU probably was never ported to Cygwin and there is obsolete
cruft to add -mno-cygwin.
Something like this is needed even if you use the cygwin-to-mingw
cross compiler:
diff --git a/configure b/configure
index 8f27ab3..bab3aa3 100755
- --- a/configure
+++ b/configure
@@ -344,6 +344,8 @@ elif check_define __sun__ ; then
targetos='SunOS'
elif check_define __HAIKU__ ; then
targetos='Haiku'
+elif check_define __MINGW32__ ; then
+ targetos='MINGW32'
else
targetos=`uname -s`
fi
Stefan, can you look at it?
Paolo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJSQbJjAAoJEBvWZb6bTYbywi4QAJmIGMhP6UfVgm1x9vDniNDF
yOT70Pp+4cOoz7C/y6RkwcGYyPs1Wvh7+AyxhAp8mb1q53gAOZRO52IXVjrk59T6
NSPG9Z8MBUrjT+yUWaUgFqHVZs6jZiULcLKjZ2gccMm/dd2TxYNwmB2LRDGYbj8C
jD2o6FFhQ6KS0c5voaTwsHtgWWPmoAII9dF45rYw9KKRb1c+glk29XjkK/D85cq6
O65PSxIP3LD80fO2gZpYezdyyzft9zhe/TFTEjXRUqMvHzQrZtEj7YDAKwvRu4Zk
3hwLU1CObnpJQtKgaBdtPnTrUcESHhqHAc9Cn5wnP2uP+Y/c2BgAmpOsfrBTA23z
SBVI6/j6api4HRBmSRTuespScspgH8pbQYMjUQNqjfyx4oVWPlqCpdKF6nGXYMis
gmSXAlBKh7eMWQH6PS/717x0SuOi3r4UVHYd9tQt8VCRvTSgcM/EH/l9IEwRRtxI
0Z244C6ghhf9xW+VILP/AGGPgfojwfyMImNc4Ph5UhZ5XVGPoOsl1Cy4X2qnYS8K
TX5qg5qZK2MOLx2uW3ni3TtHChCogiVJxJJvC7NS1JOzV3hjSUNb2NDo3etnHnKb
vNOsYgVM4AFPnJRCzPiKXLLTBX2lqoz66loFuoyJwCy1fAL7K3danlr89cQCmBmX
TwztzxhiE67xdFGhZKaG
=LWdG
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-09-24 15:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 13:56 [Qemu-devel] qemu-1.6.0 under Cygwin64 ./configure failed Alexander Voropay
2013-09-24 14:41 ` Eric Blake
2013-09-24 15:02 ` Alexander Voropay
2013-09-24 15:40 ` Paolo Bonzini [this message]
2013-09-25 20:21 ` Stefan Weil
2013-09-25 8:55 ` Alexander Voropay
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=5241B263.8060105@redhat.com \
--to=pbonzini@redhat.com \
--cc=alexander.voropay@gmail.com \
--cc=eblake@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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).