Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 32275 invoked by uid 500); 1 Jun 2001 21:26:20 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 32262 invoked from network); 1 Jun 2001 21:26:20 -0000 Date: Fri, 1 Jun 2001 14:24:26 -0700 From: "Roy T. Fielding" To: new-httpd@apache.org Subject: Re: [PATCH] TLS cleanup Message-ID: <20010601142426.C898@waka.ebuilt.net> Mail-Followup-To: "Roy T. Fielding" , new-httpd@apache.org References: <20010601152115.A2264@covalent.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.13-current-20010115i In-Reply-To: <20010601152115.A2264@covalent.net>; from rmorgan@covalent.net on Fri, Jun 01, 2001 at 03:21:15PM -0700 X-AntiVirus: scanned for viruses by AMaViS 0.2.1-pre3 (http://amavis.org/) X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N > So now all the user needs to specify is --enable-tls, and only --with-ssl=dir > if configure cannot find the SSL toolkit. That's a reasonable theory, but note that the existing tls check allows more options than the openssl check. I think we need to head in this direction but replace the existing "search for openssl" code with a simpler AC_TRY_LINK check that was specific to the minimum SSL library needed to compile those modules. ....Roy