From owner-freebsd-threads@FreeBSD.ORG  Thu Mar  3 06:46:40 2005
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
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 E829E16A4CE
	for <threads@freebsd.org>; Thu,  3 Mar 2005 06:46:40 +0000 (GMT)
Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 78E5A43D41
	for <threads@freebsd.org>; Thu,  3 Mar 2005 06:46:40 +0000 (GMT)
	(envelope-from deischen@freebsd.org)
Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11])
	j236kdgP003098;	Thu, 3 Mar 2005 01:46:39 -0500 (EST)
Date: Thu, 3 Mar 2005 01:46:39 -0500 (EST)
From: Daniel Eischen <deischen@freebsd.org>
X-X-Sender: eischen@sea.ntplx.net
To: Andriy Tkachuk <andrit@ukr.net>
In-Reply-To: <000b01c51fbb$4189ea30$090210ac@BORJA>
Message-ID: <Pine.GSO.4.43.0503030144350.234-100000@sea.ntplx.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net)
cc: threads@freebsd.org
Subject: Re: patch for threads/76690 - critical - fork hang in child for
 -lc_r
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: Daniel Eischen <deischen@freebsd.org>
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Mar 2005 06:46:41 -0000

On Thu, 3 Mar 2005, Andriy Tkachuk wrote:

>
> > Is there a reason you are still using libc_r?
>
> I don't use it at all, but there was critical bug
> i threads-pr - so i just decided to fix it since i
> have had some time )

Oh, OK.

> If this library is needless, why is it still there
> and this pr in criticals?

libc_r is marked for deprecation, but still used by some
archs (sparc64 & alpha).  Also, some folks want to use
nvidia drivers/openGL and these aren't thread-safe with
anything but libc_r.

-- 
DE