qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Turner <digit@google.com>
To: malc <av1474@comtv.ru>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH] Fix cygwin build and simplify feature detection in 'configure' script
Date: Thu, 11 Jun 2009 00:09:16 +0200	[thread overview]
Message-ID: <60cad3f0906101509l15154a82g8e1d5dc7375dce3@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0906110138170.3368@linmac.oyster.ru>

[-- Attachment #1: Type: text/plain, Size: 633 bytes --]

On Wed, Jun 10, 2009 at 11:40 PM, malc <av1474@comtv.ru> wrote:

> On Wed, 10 Jun 2009, David Turner wrote:
>
> Last time I needed to test QEMU on Windows I used cygwin and just
> configured things with: ./configure [options] --cc='gcc -mno-cygwin'
> and things just worked.
>

thanks malc, I believe the patch above should get rid of the need for the
--cc='gcc -mno-cygwin' entirely and just auto-configure things.

Looking at configure through 'git blame' shows that the
"OS_CFLAGS=-mno-cygwin" line inside it is dated January 2007.
So I presume that no one is really testing the mainline sources on Windows
on a regular basis :-(

[-- Attachment #2: Type: text/html, Size: 984 bytes --]

  reply	other threads:[~2009-06-10 22:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-10 11:53 [Qemu-devel] [PATCH] Fix cygwin build and simplify feature detection in 'configure' script David Turner
2009-06-10 20:52 ` [Qemu-devel] " David Turner
2009-06-10 21:40   ` malc
2009-06-10 22:09     ` David Turner [this message]
2009-06-10 22:17       ` Filip Navara
2009-06-10 22:29         ` David Turner
2009-06-10 23:32           ` David Turner
2009-06-11  0:53             ` David Turner
2009-06-10 22:19       ` malc
2009-06-12  2:26         ` Jamie Lokier
2009-06-12  9:55           ` Daniel P. Berrange
2009-06-12 10:36             ` Mark Cave-Ayland
2009-06-10 21:46   ` Consul
  -- strict thread matches above, loose matches on Subject: below --
2009-06-10 22:02 Teemu Nätkinniemi

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=60cad3f0906101509l15154a82g8e1d5dc7375dce3@mail.gmail.com \
    --to=digit@google.com \
    --cc=av1474@comtv.ru \
    --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).