Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 77369 invoked by uid 500); 10 Apr 2000 16:02:13 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk X-No-Archive: yes Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 77355 invoked from network); 10 Apr 2000 16:02:13 -0000 X-Authentication-Warning: koj: rbb owned process doing -bs Date: Mon, 10 Apr 2000 09:03:23 -0400 (EDT) From: rbb@covalent.net X-Sender: rbb@koj To: new-httpd@apache.org Subject: Re: [APR] Thread Lock Problem In-Reply-To: <20000410173832.H1702@deejai.mch.sni.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N On Mon, 10 Apr 2000, Martin Kraemer wrote: > If APR_HAS_THREADS == 1 but USE_PTHREAD_SERIALIZE is undefined, then > the lock functions are not DEFINED (in lib/apr/locks/unix/intraproc.c), > but they are still USED in lib/apr/locks/unix/locks.c! This should NEVER happen. Currently, the only thread locking scheme we understand is pthread serialize. If we are finding threads, then we should be using pthreads for locks. On what platform is this happening? Ryan _______________________________________________________________________________ Ryan Bloom rbb@apache.org 406 29th St. San Francisco, CA 94131 -------------------------------------------------------------------------------