From owner-svn-src-head@FreeBSD.ORG Fri Mar 20 22:17:03 2009 Return-Path: Delivered-To: svn-src-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B7EC1065672; Fri, 20 Mar 2009 22:17:03 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 229F08FC0A; Fri, 20 Mar 2009 22:17:03 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id D092646B2A; Fri, 20 Mar 2009 18:17:02 -0400 (EDT) Date: Fri, 20 Mar 2009 22:17:02 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Coleman Kane In-Reply-To: <1237573175.1993.19.camel@localhost> Message-ID: References: <200903142010.n2EKAESF006945@svn.freebsd.org> <20090320140015.GA17645@hub.freebsd.org> <20090320153405.GA62675@zim.MIT.EDU> <49C3BCD4.4030605@freebsd.org> <1237567495.1993.2.camel@localhost> <49C3D518.6070105@freebsd.org> <1237573175.1993.19.camel@localhost> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Cc: svn-src-head@freebsd.org, Vasil Dimov , svn-src-all@freebsd.org, Sam Leffler , src-committers@freebsd.org Subject: Re: svn commit: r189828 - in head: include sys/sys X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Mar 2009 22:17:03 -0000 On Fri, 20 Mar 2009, Coleman Kane wrote: > I've found that many of the GNU apps are notorious for this. I really can't > say that I know why libassuan or gnupg explicitly require GNU pth, rather > than first attempting to use POSIX pthread API. Their configure scripts both > want to search for and run pth-config, and fail to enable some sort of > threaded features if it doesn't exist. I already tried removing pth stuff > from both port Makefiles to see what would happen. I didn't spend much time > on it after I figured out that devel/pth would just work if I removed the > signal.h include. > > I am guessing that some non-standard extensions which GNU pth provides are > not provided by the normal POSIX spec. > > In fact, libassuan just goes ahead and uses a bunch of pth_* overrides for > dealing with them in a thread-safe manner (waitpid, read, write, select, > usleep). Historically, pthreads implementations were highly variable in quality, completeness, etc. It wouldn't surprise me if the persistence of applications linking against pth isn't, in part, a response to that (now-historic) situation. Robert N M Watson Computer Laboratory University of Cambridge