From owner-freebsd-hackers Tue Aug 4 19:49:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA20360 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 19:49:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA20340 for ; Tue, 4 Aug 1998 19:49:14 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id MAA12918; Wed, 5 Aug 1998 12:17:52 +0930 (CST) Message-Id: <199808050247.MAA12918@cain.gsoft.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: doconnor@gsoft.com.au (Daniel O'Connor), dag-erli@ifi.uio.no, kaleb@ics.com, hackers@FreeBSD.ORG Subject: Re: Threaded X libs.. In-reply-to: Your message of "Wed, 05 Aug 1998 02:24:53 GMT." <199808050224.TAA02476@usr02.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 Aug 1998 12:17:48 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hmm.. where could I find information on Draft xx standard? It would > > be nice to have a yardstick to measure the implementation by :) > Join a POSIX committee. 8-). Oh yes :) > The information is available in the O'Reilly Pthreads book, which has > a section on the differences between the standard and Draft 4. Aha.. Hmm.. might be an intersting read.. I wonder if my student card still works at uni =) > If FreeBSD is not full Standard, than this code will now break; the > PTHREAD_MUTEX_INITIALIZER (and the attr argument to pthread_create) > should have been the last things changes when Standard compliance > became reality). 8-(. Doh :-/ Oh well, it just means that we'll have to get around to implementing it all ;) > > I got the patched MIT threads library which has more of the standard > > implemented.. Now to rebuild XFree86 against it (urgh..) > Bad plan. The default FreeBSD libc is not threads safe for user space > threads. This means that the code will appear to work, but won't really > work. The FreeBSD libc_r overrides system call definitions, as well, > instead of merely adding pthreads functions. Yes, but I thought the whole point of the MIT pthreads package was that it overrides the system calls which aren't thread safe, with threadable wrappers. --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message