From: Jose Renau <renau@soe.ucsc.edu>
To: Phil Krylov <phil.krylov@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] block-raw.c COCOA patch
Date: Mon, 28 Aug 2006 10:47:48 -0700 [thread overview]
Message-ID: <28b85d2b8d721e337a6d1e5ad77291e4@soe.ucsc.edu> (raw)
In-Reply-To: <c10dbf450608281023w4d8f7230nf7c16530f5004a3a@mail.gmail.com>
Thanks, I did not know the CONFIG_DARWING define.
On Aug 28, 2006, at 10:23 AM, Phil Krylov wrote:
> Hi Jose,
>
> On 28/08/06, Jose Renau <renau@soe.ucsc.edu> wrote:
>>
>> --- block-raw.c 24 Aug 2006 18:58:29 -0000 1.9
>> +++ block-raw.c 28 Aug 2006 15:41:38 -0000
>> @@ -25,7 +25,11 @@
>> #include "block_int.h"
>> #include <assert.h>
>> #ifndef _WIN32
>> +#ifdef CONFIG_COCOA
>> +#include <sys/aio.h>
>> +#else
>> #include <aio.h>
>> +#endif
>
> Did you mean CONFIG_DARWIN? Qemu can be built without Cocoa.
>
> -- Ph.
>
--
Never underestimate the power of human stupidity.
- Lazarus Long
prev parent reply other threads:[~2006-08-28 17:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 15:41 [Qemu-devel] block-raw.c COCOA patch Jose Renau
2006-08-28 17:23 ` Phil Krylov
2006-08-28 17:47 ` Jose Renau [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=28b85d2b8d721e337a6d1e5ad77291e4@soe.ucsc.edu \
--to=renau@soe.ucsc.edu \
--cc=phil.krylov@gmail.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).