From owner-cvs-src@FreeBSD.ORG Sun Aug 31 19:58:37 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 CB26516A4BF for ; Sun, 31 Aug 2003 19:58:37 -0700 (PDT) Received: from smtp.mho.com (smtp.mho.net [64.58.4.6]) by mx1.FreeBSD.org (Postfix) with SMTP id BA9C843FD7 for ; Sun, 31 Aug 2003 19:58:34 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: (qmail 40701 invoked by uid 1002); 1 Sep 2003 02:58:34 -0000 Received: from unknown (HELO freebsd.org) (64.58.1.252) by smtp.mho.net with SMTP; 1 Sep 2003 02:58:34 -0000 Message-ID: <3F52B5CE.8040905@freebsd.org> Date: Sun, 31 Aug 2003 20:58:22 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3) Gecko/20030425 X-Accept-Language: en-us, en MIME-Version: 1.0 To: deischen@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Joe Marcus Clarke cc: cvs-src@freebsd.org cc: src-committers@freebsd.org 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 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:58:37 -0000 Daniel Eischen wrote: > 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. > This opens up very important questions. How do we smoothly make the transition? What is the appropriate threading library for each platform? Should 'libpthread' be a symlink, or should a library be renamed? How do we answer these last two questions in a consistent fashion? Where does libmap fit in? Scott