All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Fix compilation on MinGW Windows cross-compiler
Date: Fri, 24 Oct 2008 08:58:13 -0500	[thread overview]
Message-ID: <4901D475.9050308@codemonkey.ws> (raw)
In-Reply-To: <20081024133536.GA12450@amd.home.annexia.org>

Richard W.M. Jones wrote:
> Inspired by some comments by Anthony Liguori yesterday, I got qemu to
> compile using the Fedora MinGW cross-compiler[1].
>
> There are some problems introduced by what I think is new code (the
> migration code), so I just hacked those bits out.  Not a good fix, but
> the patch is attached anyhow.
>
> After installing the MinGW packages in Fedora[2], the command to
> compile qemu is:
>
>   PATH=/usr/i686-pc-mingw32/sys-root/mingw/bin:$PATH \
>   PKG_CONFIG_PATH=/usr/i686-pc-mingw32/sys-root/mingw/lib/pkgconfig \
>   ./configure \
>     --cross-prefix=i686-pc-mingw32- \
>     --host-cc=i686-pc-mingw32-gcc \
>     --cpu=i386 \
>     --disable-gcc-check \
>     --audio-drv-list=
>   make
>
> This produces Windows binaries (eg. qemu-system-x86_64.exe) which work
> to some extent under Wine.  In fact I was able to boot a 64 bit Fedora
> 9 guest up to the point where it runs initrd, at which point qemu
> crashes somewhere.
>
> I didn't test the binaries on real Windows.
>   

I've got a better fix locally that I'll commit.  It doesn't get 
migration working on Windows but it at least compiles.

Regards,

Anthony Liguori

> Rich.
>
> [1] http://fedoraproject.org/wiki/MinGW
> [2] http://www.annexia.org/tmp/mingw/fedora-9/
>
>   

  reply	other threads:[~2008-10-24 13:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-24 13:35 [Qemu-devel] [PATCH] Fix compilation on MinGW Windows cross-compiler Richard W.M. Jones
2008-10-24 13:58 ` Anthony Liguori [this message]
2008-10-24 14:05 ` 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=4901D475.9050308@codemonkey.ws \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.