From owner-freebsd-current@FreeBSD.ORG Wed Sep 24 03:46:38 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B3DB16A4B3 for ; Wed, 24 Sep 2003 03:46:38 -0700 (PDT) Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47F2D43F75 for ; Wed, 24 Sep 2003 03:46:37 -0700 (PDT) (envelope-from sheldonh@starjuice.net) Received: from sheldonh by axl.seasidesoftware.co.za with local (Exim 4.22) id 1A27AJ-000Jf0-27; Wed, 24 Sep 2003 12:46:35 +0200 Date: Wed, 24 Sep 2003 12:46:34 +0200 From: Sheldon Hearn To: John Birrell Message-ID: <20030924104634.GG22622@starjuice.net> Mail-Followup-To: John Birrell , current@freebsd.org References: <3F70D4EB.1080604@gmx.net> <20030924095153.GE22622@starjuice.net> <20030924101829.GG44314@freebsd1.cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030924101829.GG44314@freebsd1.cimlogic.com.au> User-Agent: Mutt/1.5.4i Sender: Sheldon Hearn cc: current@freebsd.org Subject: Re: Fixing -pthreads (Re: ports and -current) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Sep 2003 10:46:38 -0000 On (2003/09/24 20:18), John Birrell wrote: > > Okay, so what are we supposed to do to ports that are now broken because > > -pthread doesn't exist (e.g. devel/pwlib)? > > -pthread is back in current. It just had a little holiday. It's back, > refreshed, eager and willing to do the deed. 8-) That's really, REALLY good news. Will Andrews recently posted a patch on -current and mentioned that -pthread is back but will go away again soon. Can I relax and disregard his comment? :-) > > Is there a simple rule we should follow when trying to fix ports, or do > > we have to think now? > > Someone has to think and make a decision. Is simplicity (the -pthread switch) > reason enough to support one thread library by default? I'm happy with -pthread providing a simple default, which I can override if I think I know what my software really wants. :-) Ciao, Sheldon.