From: "John R. Hogerhuis" <jhoger@speakeasy.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu on windows.
Date: Thu, 18 Mar 2004 09:45:50 -0800 [thread overview]
Message-ID: <1079631950.10196.7.camel@aragorn> (raw)
In-Reply-To: <1079630604.10196.5.camel@aragorn>
[-- Attachment #1: Type: text/plain, Size: 284 bytes --]
On Thu, 2004-03-18 at 09:23, John R. Hogerhuis wrote:
> Hard part so far is using ELF format instead of PE/COFF related to
> dyngen.c, op.c (QEMU generates basic code primitives portably using GCC,
Got that backwards... for the win32 port need to use PE/COFF instead of
ELF...
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-03-18 17:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 9:37 [Qemu-devel] qemu on windows Sami Haahtinen
2004-03-18 10:07 ` [Qemu-devel] " Sami Haahtinen
2004-03-18 17:23 ` [Qemu-devel] " John R. Hogerhuis
2004-03-18 17:45 ` John R. Hogerhuis [this message]
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=1079631950.10196.7.camel@aragorn \
--to=jhoger@speakeasy.net \
--cc=jhoger@pobox.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).