From owner-cvs-src@FreeBSD.ORG Sun Aug 31 19:51:12 2003 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF59316A4BF; Sun, 31 Aug 2003 19:51:12 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id DAA9543FDD; Sun, 31 Aug 2003 19:51:11 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.8/8.12.1) with ESMTP id h812pBtp016914; Sun, 31 Aug 2003 22:51:11 -0400 (EDT) Date: Sun, 31 Aug 2003 22:51:11 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Joe Marcus Clarke In-Reply-To: <1062382220.42216.6.camel@shumai.marcuscom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: cvs-src@freebsd.org cc: src-committers@freebsd.org cc: Scott Long cc: cvs-all@freebsd.org Subject: Re: cvs commit: src/contrib/gcc/config freebsd-spec.h X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: deischen@freebsd.org List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Sep 2003 02:51:12 -0000 On Sun, 31 Aug 2003, Joe Marcus Clarke wrote: > On Sun, 2003-08-31 at 22:05, Scott Long wrote: > > Daniel Eischen wrote: > > > deischen 2003/08/31 15:38:52 PDT > > > > > > FreeBSD src repository > > > > > > Modified files: > > > contrib/gcc/config freebsd-spec.h > > > Log: > > > Remove -pthread as a compiler option. It was deprecated 2.5 years > > > ago, but not removed. > > > > > > No reply from: threads, kan, obrien > > > > > > Revision Changes Path > > > 1.10 +2 -38 src/contrib/gcc/config/freebsd-spec.h > > > > > > > What is the consequence of this on ports/? I'm very much in > > favor of this change, but I'm wondering if more safety belts are > > needed. Also, are there any consequences on the doc/ and www/ > > areas? I don't know, but it hasn't been -pthread in current in over 2.5 years. Yes, -pthread was there as a bandaid, but it wasn't _the_ way to build threaded applications under -current. So, -pthread _was_ the safety belt. > I have a feeling we will see an increase of port build errors on > -CURRENT. This may not be a bad thing, though. It will show us which > ports are not using ${PTHREAD_LIBS} correctly. I agree. This is only the first step, though. Once ports get through this, there may be another hurdle once libkse becomes libpthread again. Autoconf may autodetect the presence of a libpthread and link to it, in conjunction with linking to ${PTHREAD_LIBS} being picked up somewhere else in the port. Just try building XFree86-4 or kde with libpthread (libkse installed as libpthread) and ${PTHREAD_LIBS} set to libc_r. It links to both libraries. -- Dan Eischen