Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Message-ID: <3EC8E488.6030103@attglobal.net>
Date: Mon, 19 May 2003 10:04:56 -0400
From: Jeff Trawick <trawick@attglobal.net>
Reply-To: trawick@attglobal.net
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.3) Gecko/20030312
MIME-Version: 1.0
To: dev@httpd.apache.org
Subject: Re: Building mod_deflate against libz.a (static)
References: <5.2.0.9.2.20030519082112.0458e9f0@pop3.rowe-clan.net>
In-Reply-To: <5.2.0.9.2.20030519082112.0458e9f0@pop3.rowe-clan.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

William A. Rowe, Jr. wrote:

>   Attached is a trivial patch that looks at the contents of zlib_base/lib
> to make this determination.  It then adds the libz.a to the objects list
> to build mod_deflate, provided we don't recognize the shlib extension.
> This is not 100% portable behavior, but very useful on the majority of
> platforms which support it.

Which part of your patch prevents this from happening on the platforms 
that don't support it?  (ISTR static linking of zlib with mod_deflate 
not doing the right thing on HP-UX.)

Does it break normal users to do it the portable way?