From owner-freebsd-threads@FreeBSD.ORG Thu Feb 3 22:06:58 2005 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7910A16A4CE; Thu, 3 Feb 2005 22:06:58 +0000 (GMT) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6E5743D2D; Thu, 3 Feb 2005 22:06:57 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) j13M6u0w002435; Thu, 3 Feb 2005 17:06:56 -0500 (EST) Date: Thu, 3 Feb 2005 17:06:56 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: John Baldwin In-Reply-To: <200502031644.19695.jhb@FreeBSD.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) cc: threads@freebsd.org Subject: Re: Backport of pthread fixes from 5.x to 6.0. X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Daniel Eischen List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Feb 2005 22:06:58 -0000 On Thu, 3 Feb 2005, John Baldwin wrote: > On Tuesday 01 February 2005 11:20 am, Daniel Eischen wrote: > > On Tue, 1 Feb 2005, John Baldwin wrote: > > > I'd like to backport most of the thread fixes for libpthread from 6.0 to > > > RELENG_5 before 5.4. I've been testing this patch locally and just > > > wanted to make sure backporting it was ok with the folks on this list. > > > Patch is at http://www.FreeBSD.org/~jhb/patches/pthread_5.patch > > > > Yes, please :-) This was one of the things I had wanted to do but hadn't > > got around to yet. > > I have a question about the ABI changes (granted, to internal symbols) that > break www/linuxpluginwrapper. Has the port been updated so that it works > now? If not, do I need to include the patch you mentioned as a workaround > for this in the commit log when I MFC to RELENG_5? The port has been updated, so it should work just fine. -- DE