From owner-freebsd-current@FreeBSD.ORG Sat Sep 20 19:40: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 61BD316A4B3; Sat, 20 Sep 2003 19:40:38 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 69CF443F75; Sat, 20 Sep 2003 19:40:37 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.9p1/8.12.3) with ESMTP id h8L2eaGA018607; Sat, 20 Sep 2003 20:40:36 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sat, 20 Sep 2003 20:40:37 -0600 (MDT) Message-Id: <20030920.204037.86014076.imp@bsdimp.com> To: kris@obsecurity.org From: "M. Warner Losh" In-Reply-To: <20030921022407.GA39970@rot13.obsecurity.org> References: <20030920.164621.68039520.imp@bsdimp.com> <20030921022407.GA39970@rot13.obsecurity.org> X-Mailer: Mew version 2.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: deischen@freebsd.org cc: current@freebsd.org cc: h@schmalzbauer.de Subject: Re: Fixing -pthreads 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: Sun, 21 Sep 2003 02:40:38 -0000 In message: <20030921022407.GA39970@rot13.obsecurity.org> Kris Kennaway writes: : 1) Put back -pthread in -current so all the ports don't fail I've been thinking about just doing that, but was holding off to make sure people had a chance to do this in the absense of dragging out a big stick. : 2) I will build a full set of -current packages with the -pthread : error still in place, to determine the list of packages that need to : be fixed (in fact I already have this, see : http://dosirak.kr.freebsd.org/errorlogs). : : 3) You, John Birrell, and whoever else is interested in fixing these : ports can work on them at your own pace without disrupting life for : the rest of the users. Once they're all fixed, we can turn the error : back on or make it a NOP or do whatever else is decided to be : appropriate. : : 4) It is likely that steps 2 and 3 will need to be iterated several : times, because there are dozens of ports that need to be fixed, and : many of them are hiding other ports that depend on them and also need : to be fixed. I think this is an excellent plan. Warner