From owner-freebsd-hackers Tue Jul 14 11:22:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA15756 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 11:22:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from phoenix.volant.org (phoenix.volant.org [205.179.79.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA15751 for ; Tue, 14 Jul 1998 11:22:38 -0700 (PDT) (envelope-from patl@phoenix.volant.org) From: patl@phoenix.volant.org Received: from asimov.phoenix.volant.org ([205.179.79.65]) by phoenix.volant.org with smtp (Exim 1.92 #8) id 0yw9ig-0005mE-00; Tue, 14 Jul 1998 11:22:30 -0700 Received: from localhost by asimov.phoenix.volant.org (SMI-8.6/SMI-SVR4) id LAA04384; Tue, 14 Jul 1998 11:22:14 -0700 Date: Tue, 14 Jul 1998 11:22:13 -0700 (PDT) Reply-To: patl@phoenix.volant.org Subject: Re: Detecting the presence of threads (for a port) To: Peter van Heusden cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter van Heusden wrote (in a slightly different order): > P.S. Who else (if anyone) is working on ldap at present? I've been working on setting up some LDAP-based facilities for my virtual domain customers. I haven't really dug into the ldap sources much though. > I've been merging Terry Lambert's patches to ldap-3.3 (which include the > Critical Angle patches as well as some of Terry's own) with the existing > ldap port, and managed to get a working build (which needs an hour or two > of cleaning up). The port, however, requires pthreads, which requires > libc_r. I was wondering how to deal with this. Two questions: > > 1) How to detect the existence of pthreads? I assume a pre-configure test > for libc_r should do? > > 2) Should pthreads be required in the default port? Since they are not > available with an out-of-the-box 2.2 FreeBSD, I assume not, in which case > I'd have to break the pthread patches out into a seperate set of files, > and only apply them if a particular make variable is set. Does this make > sense? Hmmm. If pthreads were a port; I'd say just make it a dependancy and let the build auto-install it. On the whole, I'm inclined to go ahead and require it. Add a test to the top-level Makefile that emits a message and aborts if it can't find libc_r or pthread.h. The message should briefly indicate how to install pthreads; or at least where to find that info. -Pat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message