From owner-freebsd-threads@FreeBSD.ORG Thu Nov 13 10:33:10 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 83FAA16A4CE for ; Thu, 13 Nov 2003 10:33:10 -0800 (PST) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3AAB843FF5 for ; Thu, 13 Nov 2003 10:33:09 -0800 (PST) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id hADIX31G004933; Thu, 13 Nov 2003 13:33:03 -0500 (EST) Date: Thu, 13 Nov 2003 13:33:03 -0500 (EST) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Craig Rodrigues In-Reply-To: <20031113170801.GA8760@crodrigues.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-threads@freebsd.org Subject: Re: Comments about FreeBSD threading from Apache people 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: Thu, 13 Nov 2003 18:33:10 -0000 On Thu, 13 Nov 2003, Craig Rodrigues wrote: > On Thu, Nov 13, 2003 at 01:51:00AM -0500, Daniel Eischen wrote: > > Supposedly, libkse will be default for archs in which > > it is supported (currently i386, amd64, ia64) for > > 5.2-RELEASE. > > What is the release criteria for this? Is re@ going > to make this decision? Yes. > > It is undecided whether it will be default > > by means of installing an appropriate libmap.conf, or > > by renaming libkse back to libpthread and changing > > PTHREAD_LIBS to -lpthread (and also changing gcc -pthread > > so that it links to libpthread instead of libc_r). > > Hmm, this is indeed a tricky thing, and I don't know > the best course of action to recommend. Where is > the best place to follow discussion related to this? I dunno; ask re@. It's their call. I don't really care one way or the other for 5.2-release, but for 5.3 libkse will going out as libthread. > > Port maintainers shouldn't get too concerned about > > this; they should continue to rely on PTHREAD_LIBS > > and PTHREAD_CFLAGS. I suppose there is the possibility > > that some ports may want a specific threads library. > > In that case, perhaps PTHREAD_LIBS can be overridden > > by the port. But you should probably ask ports@ > > to see if that is how it should be handled. > > Well, for just maintaining a port, it is OK. > However, for pushing changes back to the original > package maintainers, you cannot really rely on > PTHREAD_LIBS and PTHREAD_CFLAGS, because those > variables are defined in /usr/ports/Mk/bsd.port.mk. Don't use -lkse somewhere outside our ports tree; it is just a temporary name. In the future, whether it's 5.2 or 5.3, it will be libpthread. Autoconf/configure/etc scripts should first check for the presence of libpthread, then libc_r. Things that don't use autoconf et. al. can always check the FreeBSD version (we'll bump it when libkse becomes libpthread). -- Dan Eischen