From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org
Cc: haikuports-devs@ports.haiku-files.org
Subject: Re: [Qemu-devel] Re: [PATCH] [RFC] Haiku host support and general configure issues
Date: Sat, 28 Feb 2009 20:26:13 +0000 [thread overview]
Message-ID: <20090228202613.GI20640@shareable.org> (raw)
In-Reply-To: <DC042C64-ECA8-43BA-A999-1E39CDE635B5@web.de>
Andreas Färber wrote:
> Hm, the so-called AIO check is rather a pthreads check:
>
> #include <pthread.h>
> int main(void) { pthread_mutex_t lock; return 0; }
>
> If that compiles, a working -lpthread is assumed. It's buggy in itself
> because it first sets AIOLIBS="", then compiles with unchanged empty
> $AIOLIBS and then sets AIOLIBS="-lpthread".
>
> >>AIOLIBS is set to -lpthread but that is not available on Haiku.
> >
> >Well we should have a pthread lib available though...
Note that "-lpthread" is not even a portable way to get pthreads -
even if it links successfully, it need not behave correctly. (Think
of libc having different versions for threads and no-threads).
Maybe that's why Haiku doesn't have -lpthread.
-- Jamie
next prev parent reply other threads:[~2009-02-28 20:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-28 14:08 [Qemu-devel] [PATCH] [RFC] Haiku host support and general configure issues Andreas Färber
2009-02-28 17:08 ` [Qemu-devel] " François Revol
2009-02-28 18:31 ` Andreas Färber
2009-02-28 19:01 ` [HaikuPorts-devs] " François Revol
2009-02-28 20:26 ` Jamie Lokier [this message]
2009-02-28 20:32 ` François Revol
2009-03-08 18:15 ` Anthony Liguori
2009-03-08 18:41 ` [HaikuPorts-devs] " François Revol
2009-03-09 8:40 ` Avi Kivity
2009-03-09 14:14 ` [HaikuPorts-devs] " François Revol
2009-03-09 14:33 ` Avi Kivity
2009-03-09 15:39 ` François Revol
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=20090228202613.GI20640@shareable.org \
--to=jamie@shareable.org \
--cc=haikuports-devs@ports.haiku-files.org \
--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.