From owner-freebsd-current@FreeBSD.ORG  Wed Mar 31 22:17:55 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 780AA16A4CE; Wed, 31 Mar 2004 22:17:55 -0800 (PST)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 0DDA043D3F; Wed, 31 Mar 2004 22:17:55 -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 i316Hetf001866;
	Thu, 1 Apr 2004 01:17:41 -0500 (EST)
Date: Thu, 1 Apr 2004 01:17:40 -0500 (EST)
From: Daniel Eischen <eischen@vigrid.com>
X-Sender: eischen@pcnet5.pcnet.com
To: Oliver Eikemeier <eikemeier@fillmore-labs.com>
In-Reply-To: <406B697E.6080309@fillmore-labs.com>
Message-ID: <Pine.GSO.4.10.10404010116230.265-100000@pcnet5.pcnet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: "Jacques A. Vidrine" <nectar@FreeBSD.org>
cc: freebsd-current@FreeBSD.org
cc: Sean McNeil <sean@mcneil.com>
Subject: Re: nss_ldap broken
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Apr 2004 06:17:55 -0000

On Thu, 1 Apr 2004, Oliver Eikemeier wrote:

> Daniel Eischen wrote:
> 
> > Too bad these shared libraries can't be made to use
> > the libgcc trick, so they can still be thread-safe
> > but not depend on a threads library.
> 
> Sorry to ask stpid questions, but what is `the libgcc
> trick' here?

See one of my previous posts to this thread WRT #pragma weak.

Another option pointed out, is just to make sure libc
has all the necessary hooks (I think it does) and don't
link shared libraries to libpthread.

-- 
Dan Eischen