All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: Sebastian Herbszt <herbszt@gmx.de>
Cc: "Anthony Liguori" <aliguori@us.ibm.com>,
	"Marcelo Tosatti" <mtosatti@redhat.com>,
	qemu-devel@nongnu.org, "Teemu Nätkinniemi" <stinkf42@yahoo.com>
Subject: Re: [Qemu-devel] Re: Threads and win32
Date: Tue, 21 Jul 2009 13:58:46 +0100	[thread overview]
Message-ID: <20090721125846.GG20756@shareable.org> (raw)
In-Reply-To: <E024B6C880944EB4A5E8C2399F5EA5BC@FSCPC>

Sebastian Herbszt wrote:
> vl.c:3873: warning: implicit declaration of function `sigaction'
> vl.c:3887: error: `SIGUSR1' undeclared (first use in this function)
> vl.c:3881: error: `SIGUSR2' undeclared (first use in this function)
> vl.c:3882: error: `SIGIO' undeclared (first use in this function)
> vl.c:3883: error: `SIGALRM' undeclared (first use in this function)

It's not surprising.

WIN32 doesn't have unix-style signals :-)

WIN32 doesn't have pthreads either, but there's a
pthread-compatibility library people often use.  That provides
pthreads emulation but not signal emulation.  WIN32 does provide
threads and locking primitives, and it's not too painful to build
pthreads on t top of that.

To emulate signals you really have to use Cygwin or one of the other
unix-on-WIN32 emulation packages.  Or change the code to not use signals.

WIN32 has native async I/O, by the way.  I don't know if it's
suitable, especially since we found how broken Linux async I/O is
despite the simple API, but Windows has had it since the early 90s
(all versions derived from Windows NT) and inherited the design from
VMS, so it's probably in good shape.

-- Jamie

  reply	other threads:[~2009-07-21 12:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-18 19:27 [Qemu-devel] Threads and win32 Teemu Nätkinniemi
2009-07-19 12:11 ` [Qemu-devel] " Sebastian Herbszt
2009-07-20 16:07   ` Marcelo Tosatti
2009-07-20 19:09     ` Sebastian Herbszt
2009-07-20 23:52       ` Marcelo Tosatti
2009-07-21 12:11         ` Sebastian Herbszt
2009-07-21 12:58           ` Jamie Lokier [this message]
2009-07-21 13:22           ` 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=20090721125846.GG20756@shareable.org \
    --to=jamie@shareable.org \
    --cc=aliguori@us.ibm.com \
    --cc=herbszt@gmx.de \
    --cc=mtosatti@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stinkf42@yahoo.com \
    /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.