Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 27168 invoked by uid 6000); 22 Dec 1999 19:23:06 -0000 Received: (qmail 27148 invoked from network); 22 Dec 1999 19:23:03 -0000 Received: from slarti.muc.de (193.149.48.10) by taz.hyperreal.org with SMTP; 22 Dec 1999 19:23:03 -0000 Received: (qmail 25086 invoked by uid 66); 22 Dec 1999 19:22:30 -0000 Received: from en by slarti with UUCP; Wed Dec 22 19:22:30 1999 -0000 Received: by en1.engelschall.com (Sendmail 8.9.3+3.2W) for new-httpd@apache.org id UAA74432; Wed, 22 Dec 1999 20:19:03 +0100 (CET) Date: Wed, 22 Dec 1999 20:19:03 +0100 From: "Ralf S. Engelschall" To: new-httpd@apache.org Subject: Re: cvs commit: apache-2.0/src Configure Message-ID: <19991222201903.A74418@engelschall.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Organization: Engelschall, Germany. X-Web-Homepage: http://www.engelschall.com/ X-PGP-Public-Key: https://www.engelschall.com/ho/rse/pgprse.asc X-PGP-Fingerprint: 00 C9 21 8E D1 AB 70 37 DD 67 A2 3A 0A 6F 8D A5 Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org Status: O In article you wrote: > >> BTW, will non-system thread libraries like Pth even work with 2.0 >> right now? I'm mostly worried about APR, because I don't know if >> anyone has had the time to implement that yet. >> >> The autoconf setup in Apache has the same problem. PHP4 seems to let >> you choose pthreads, Pth, or whatever. I guess it wouldn't be hard to >> make the pthread-checking macro also support --with-pth. > > The proper solution, is to add a Pth library for APR. APR has been setup > to allow for building with a different threading library. Nobody has > implemented the APR layer for a threading library other than pthreads, so > APR's configure only recognizes --enable-threads=pthread or > --disable-threads. If we ever get around to putting Pth into APR, we'll > also support --enable-threads=pth. Errr.... you actually don't have to use the native Pth API. It's fine if Apache 2.0 uses Pth's Pthread API (which is an API also provided by Pth which already provides a mapping from Pthreads to native Pth API). So, the problem for APR is not the use of the Pthreads API (Pth implements here actually most of the stuff). The problem is just that hardcoding things like -pthread is wrong, because for using Pth you need $ CFLAGS="`pthread-config --cflags`" \ LDFLAGS="`pthread-config --ldflags --libs`" \ ./configure which usually conflicts with a hard-coded -pthread. So all which Apache 2.0 has to do is to be more flexible in choosing the Pthread library. Using -pthread should be only a _fallback_, but not the default. Ralf S. Engelschall rse@engelschall.com www.engelschall.com