X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Sat, 30 Jul 2011 12:22:49 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Pthread error? Message-ID: <20110730102249.GJ26203@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Jul 30 05:52, Jan Chludzinski wrote: > > pthread_getthreadid_np is a non-standard IBM extension. You won't find > > it in the POSIX specs. > > Does Cygwin support the full POSIX pthread spec? That would be nice, but, no, not yet. See http://cygwin.com/cygwin-api/compatibility.html In the next Cygwin version 1.7.10, most of the missing pthread functions from http://cygwin.com/cygwin-api/std-notimpl.html will have been added. Still missing for 1.7.10 since nobody implemented them yet are pthread_barrier[...] pthread_mutexattr_getrobust pthread_mutexattr_setrobust pthread_mutex_consistent pthread_mutex_timedlock pthread_rwlock_timedrdlock pthread_rwlock_timedwrlock In theory, except for the barrier functions, they shouldn't be very hard to implement. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple