From owner-freebsd-threads@FreeBSD.ORG Wed Oct 5 06:02:54 2005 Return-Path: X-Original-To: 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 ABB4216A41F for ; Wed, 5 Oct 2005 06:02:54 +0000 (GMT) (envelope-from mi+kde@aldan.algebra.com) Received: from blue.virtual-estates.net (aldan.algebra.com [216.254.65.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CE2F43D49 for ; Wed, 5 Oct 2005 06:02:51 +0000 (GMT) (envelope-from mi+kde@aldan.algebra.com) Received: from blue.virtual-estates.net (blue [127.0.0.1]) by blue.virtual-estates.net (8.13.4/8.13.4) with ESMTP id j9562b3B072003 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Oct 2005 02:02:41 -0400 (EDT) (envelope-from mi+kde@aldan.algebra.com) Received: from localhost (localhost [[UNIX: localhost]]) by blue.virtual-estates.net (8.13.4/8.13.4/Submit) id j9562aU8072002; Wed, 5 Oct 2005 02:02:36 -0400 (EDT) (envelope-from mi+kde@aldan.algebra.com) X-Authentication-Warning: blue.virtual-estates.net: mi set sender to mi+kde@aldan.algebra.com using -f From: Mikhail Teterin To: threads@freebsd.org Date: Wed, 5 Oct 2005 02:02:36 -0400 User-Agent: KMail/1.8.2 X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7whJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Cc: jim@corebsd.or.id Subject: Non-threaded app dlopen-ing a thread-using library X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2005 06:02:54 -0000 Hello! I'm trying to improve the security/xmlsec1 port to support the nss-backend (which vendor supports, but the port does not). Nss (security/nss) use nspr (devel/nspr), which uses threads. The xmlsec1 executable, built by the security/xmlsec1 port is not multi-threaded by itself, but it is opening the specified back-ends at run-time. Do I need to make the executable itself multi-threaded -- just in case it needs to dlopen() a thread-using library, or is there a better way? Its other possible back-ends -- OpenSSL and GNUTLS -- do not use threads. Thanks! -mi