public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Dave Brolley <brolley@redhat.com>
To: cygwin@sources.redhat.com
Cc: jjohnstn@redhat.com
Subject: pthreads on Cygwin
Date: Mon, 22 Jan 2001 15:10:00 -0000	[thread overview]
Message-ID: <3A6CBEAA.4000002@redhat.com> (raw)

Hi,

According to the online documentation, basic pthread support is 
available on Cygwin: 
http://sources.redhat.com/cygwin/cygwin-api/std-posix.html#AEN85

I've found and #included <pthread.h> in /usr/include/pthread.h, however,
<sys/features.h>, found in /usr/include/sys/features.h, only turns on 
_POSIX_THREADS if
a macro named __rtems__ is defined. Similarly for the thread support in 
<sys/types.h>.

Is this a bug in the headers or is thread support really not there for 
vanilla Cygwin? I'm using version 1.1.7 on Windows 95. (Actually, it's a 
snapshot from Jan 10 -- I as trying to avoid the "cygwin hangs after 
'sed' in 'libtool' during builds problem). I was told by an insider that 
<pthread.h> and <sys/features.h> were only recently added.

Dave


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

             reply	other threads:[~2001-01-22 15:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-22 15:10 Dave Brolley [this message]
2001-01-22 19:01 ` Christopher Faylor
  -- strict thread matches above, loose matches on Subject: below --
2001-09-04  5:42 pthreads on cygwin Jacob Vennervald Madsen
2001-09-04  5:48 ` Robert Collins
2001-09-04  5:37 Jacob Vennervald Madsen
2001-09-04  5:40 ` Robert Collins
2001-09-04  3:00 Jacob Vennervald Madsen
2001-09-04  5:32 ` Robert Collins
2001-01-23 13:44 pthreads on Cygwin Dave Brolley
2001-01-23 14:06 ` Christopher Faylor
2001-01-14 17:04 Pthreads " Georg Waldschmidt
2001-01-15  7:18 ` Larry Hall (RFK Partners, Inc)

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=3A6CBEAA.4000002@redhat.com \
    --to=brolley@redhat.com \
    --cc=cygwin@sources.redhat.com \
    --cc=jjohnstn@redhat.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).