Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
From: Jim Jagielski <jim@jaguNET.com>
Message-Id: <200409071700.i87H0mO03179@devsys.jaguNET.com>
Subject: Re: [PATCH] Allow mod_cache to be build/loaded as DSO
To: dev@httpd.apache.org
Date: Tue, 7 Sep 2004 13:00:40 -0400 (EDT)
Reply-To: jim@jaguNET.com
In-Reply-To: <20040907150113.GA18276@redhat.com> from "Joe Orton" at Sep 07,
 2004 04:01:13 PM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

True, but this is one that I'm hitting a lot, especially
with the increase in cache development going on...

And this is the only bundled module that I've hit this on
when httpd is build "normally".

Joe Orton wrote:
> 
> On Tue, Sep 07, 2004 at 10:03:39AM -0400, Jim Jagielski wrote:
> > Jeff Trawick wrote:
> > > If you add libgcc.a into any DSO, wouldn't that take care of the
> > > issue?  (does the SH_LIBS variable allow you to specify extra
> > > libraries that should be linked into DSOs?)
> > 
> > I'm thinking specifically about preventing the dependency on libgcc.
> > Important for those who bundle/redistribute httpd :)
> 
> You can't second guess when you'll introduce a dependency on libgcc
> especially with all the 64-bit arithmetic using apr_time_t.  Build GCC
> without a shared libgcc and you can be sure to avoid any extra run-time
> dependency, of course.
> 
> joe
> 


-- 
===========================================================================
   Jim Jagielski   [|]   jim@jaguNET.com   [|]   http://www.jaguNET.com/
      "A society that will trade a little liberty for a little order
             will lose both and deserve neither" - T.Jefferson