From owner-freebsd-current@FreeBSD.ORG Sat Sep 20 17:59:42 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 862FC16A4B3; Sat, 20 Sep 2003 17:59:42 -0700 (PDT) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E2EB43FE3; Sat, 20 Sep 2003 17:59:41 -0700 (PDT) (envelope-from DougB@freebsd.org) Received: from master.dougb.net (12-234-17-181.client.attbi.com[12.234.17.181]) by comcast.net (sccrmhc13) with SMTP id <20030921005940016007hg5ke>; Sun, 21 Sep 2003 00:59:40 +0000 Date: Sat, 20 Sep 2003 17:59:39 -0700 (PDT) From: Doug Barton To: deischen@freebsd.org In-Reply-To: Message-ID: <20030920175306.Q9576@znfgre.qbhto.arg> References: Organization: http://www.FreeBSD.org/ X-message-flag: Outlook -- Not just for spreading viruses anymore! MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org cc: "M. Warner Losh" cc: h@schmalzbauer.de Subject: 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: Sun, 21 Sep 2003 00:59:42 -0000 On Sat, 20 Sep 2003, Daniel Eischen wrote: > On Sat, 20 Sep 2003, M. Warner Losh wrote: > > > In message: <3F6BF02F.9040707@schmalzbauer.de> > > Harald Schmalzbauer writes: > > : Not only the -pthread removement broke countless ports (some of them are > > > > Maybe I missed the reason why FreeBSD needs to be unique wrt threading > > programs and not have -pthread... > > Because -pthread allows selection of one specific threadling library, > not multiple. It is also unnecessary since the library is specified > as a link option, not a compiler option. In the future, -pthread > will be a NOOP, but it suits us now to have it cause an error so > that ports that don't honor PTHREAD_LIBS can be found and fixed. IF this is a good idea (and I'm not convinced it is), I still have two major objections to it. First, this action was taken with very little (any?) discussion. Second, the timing is truly horrible, occurring during a ports freeze. If your goal is actually to find and fix broken ports, there are a LOT of other options, including enlisting volunteers, and using the package building cluster. I'd really like to see this change backed out, at minimum until the ports freeze is over. Doug -- This .signature sanitized for your protection