From owner-freebsd-threads@FreeBSD.ORG Thu Nov 6 19:04:26 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 84EF716A4CE for ; Thu, 6 Nov 2003 19:04:26 -0800 (PST) Received: from net1.gendyn.com (204.60.171.22.ded.snet.net [204.60.171.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 613B743FBF for ; Thu, 6 Nov 2003 19:04:25 -0800 (PST) (envelope-from deischen@freebsd.org) Received: from plunger.gdeb.com ([153.11.11.3] helo=ebnext01) by net1.gendyn.com with esmtp (Exim 2.12 #1) id 1AHwuw-000FvX-00 for threads@freebsd.org; Thu, 6 Nov 2003 22:04:10 -0500 Received: from clcrtr.gdeb.com ([153.11.109.11]) by ebnext01 with SMTP id hA7349M2021774; Thu, 6 Nov 2003 22:04:09 -0500 Received: from freebsd.org (gpz.clc.gdeb.com [192.168.3.12]) by clcrtr.gdeb.com (8.11.4/8.11.4) with ESMTP id hA7352h82479; Thu, 6 Nov 2003 22:05:03 -0500 (EST) (envelope-from deischen@freebsd.org) Message-ID: <3FAB0B57.6050001@freebsd.org> Date: Thu, 06 Nov 2003 22:02:47 -0500 From: Dan Eischen User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Craig Rodrigues References: <20031105042423.GA1527@crodrigues.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: threads@freebsd.org Subject: Re: Why -D_THREAD_SAFE? X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2003 03:04:26 -0000 Craig Rodrigues wrote: > Hi, > > In /usr/ports/Mk/bsd.port.mk there is this: > > .if ${OSVERSION} < 500016 > PTHREAD_CFLAGS= -D_THREAD_SAFE > PTHREAD_LIBS= -pthread > .else > PTHREAD_CFLAGS= -D_THREAD_SAFE > PTHREAD_LIBS= -lc_r > .endif > > > I understand that -pthread has been deprecated > in gcc in -CURRENT. Why is -D_THREAD_SAFE > needed? It's not needed, but it isn't hurting anything either. The ports team should probably remove it. -- Dan Eischen