Date: Wed, 7 Jan 1998 20:11:37 +1100 (EST) From: John Birrell <jb@freebsd1.cimlogic.com.au> To: tg@ihf.rwth-aachen.de (Thomas Gellekum) Cc: tg@FreeBSD.ORG, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-ports@FreeBSD.ORG Subject: Re: cvs commit: ports/lang/python Makefile ports/lang/python/patches patch-ab Message-ID: <199801070911.UAA11648@freebsd1.cimlogic.com.au> In-Reply-To: <87u3bgwtdy.fsf@ghpc6.ihf.rwth-aachen.de> from Thomas Gellekum at "Jan 7, 98 10:00:40 am"
next in thread | previous in thread | raw e-mail | index | archive | help
Thomas Gellekum wrote: > John Birrell <jb@freebsd1.cimlogic.com.au> writes: > > > > Make python work with threads again. Looks like our libc_r implements > > > an older draft of the pthread standard. > > > > Yes it does. That will change with the move to kernel threads. > > libpthread will implement the standard as published (1003.1, 1996 Edition). > > That means the new library won't be in 2.2.x? Ah, yes thats correct. > > BTW, the manual page already seems to reflect the standard. At least > the published prototype for pthread_detach() doesn't match the actual > source: > > pthread.3: int pthread_detach(pthread_t thread) > pthread.h: int pthread_detach __P((pthread_t *)); Hmmm, we probably should fix this so that 2.2.x is accurate. And then ditch it. 8-) There are quite a few places where libc_r returns -1 on error and sets errno. The standard does not touch errno and the functions return a value != 0 on error. So you actually have to run the code through and error condition to find that it's not accurate. And it depend on how the code is actually coded as to how it behaves. > > tg > -- John Birrell - jb@cimlogic.com.au; jb@netbsd.org; jb@freebsd.org CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199801070911.UAA11648>