From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 06:38:35 2004 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 4ABCC16A4CE; Fri, 30 Jan 2004 06:38:35 -0800 (PST) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id B17A743D1F; Fri, 30 Jan 2004 06:38:32 -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 i0UEcWiw016551; Fri, 30 Jan 2004 09:38:32 -0500 (EST) Date: Fri, 30 Jan 2004 09:38:32 -0500 (EST) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: "Jacques A. Vidrine" In-Reply-To: <20040130142603.GE99895@madman.celabo.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: ports@FreeBSD.org cc: current@FreeBSD.org Subject: Re: HEADS UP: libkse -> libpthread switch 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: Fri, 30 Jan 2004 14:38:35 -0000 On Fri, 30 Jan 2004, Jacques A. Vidrine wrote: > On Fri, Jan 30, 2004 at 07:34:02AM -0500, Daniel Eischen wrote: > > Until > > the ports system is updated to handle this change, it is > > recommended that folks install an /etc/libmap.conf(5) that > > maps libc_r to libpthread. > > Why, exactly? (curious) > > IMHO it is unacceptable to require /etc/libmap.conf to exist. I know > this is temporary, but I hope it is *really* temporary. When you start [re]building ports now, they may pick up libpthread instead of PTHREAD_LIBS (currently -lc_r). Then you may have things linked to both libc_r and libpthread, or new applications may depend on libraries that were linked to libc_r. You can't depend on more than one threads library. I suspect it's going to be a mess for a while, but use of an appropriate libmap.conf should make things usable again. After ports catches up to these changes and you rebuild all your ports with the new threads library, then you'll no longer need the libmap.conf. Unless you have nvidia provided drivers/libraries. -- Dan Eischen