All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Lev Lvovsky <lists2@sonous.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] posix-aio-compat error in 5996
Date: Thu, 18 Dec 2008 11:24:16 -0600	[thread overview]
Message-ID: <494A8740.4030504@codemonkey.ws> (raw)
In-Reply-To: <475C9C94-175B-4FB4-9368-15F8F8BBCCA2@sonous.com>

Lev Lvovsky wrote:
> Anthony,
>
> On Dec 17, 2008, at 5:36 PM, Anthony Liguori wrote:
>
>> Lev Lvovsky wrote:
>>> On OSX 10.5, I get the following error when compiling with revision 
>>> 5996 and higher (5995 compiles).
>>>
>>> As referenced in the initial RFC 
>>> (http://lists.gnu.org/archive/html/qemu-devel/2008-12/msg00204.html), 
>>> BSD's may not need this - is there any way to avoid using this based 
>>> on OS, or is there something I'm missing in the configure options?
>>
>> Have I mentioned that I strongly dislike OS X?
>>
>> sigqueue is posix, does anyone know of the alternative function to 
>> use for OS X?  I guess we could use kill.
>
> as I wrote to M. Losh, I should have checked the patch in the original 
> RFC, which clearly had a conditional in the makefile for CONFIG_AIO.  
> Running configure with --disable-aio compiled.

I still would like it to work for OS X.  If someone can write up a patch 
replacing sigqueue with the appropriate OS X function, I'd happily apply it.

Regards,

Anthony Liguori

> thanks!
> -lev
>

  reply	other threads:[~2008-12-18 17:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-18  0:16 [Qemu-devel] posix-aio-compat error in 5996 Lev Lvovsky
2008-12-18  1:36 ` Anthony Liguori
2008-12-18 17:17   ` Lev Lvovsky
2008-12-18 17:24     ` Anthony Liguori [this message]
2008-12-18 21:24       ` Juergen Lock
2008-12-18  2:29 ` M. Warner Losh
  -- strict thread matches above, loose matches on Subject: below --
2008-12-17 17:36 Lev Lvovsky

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=494A8740.4030504@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=lists2@sonous.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 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.