httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Trawick <>
Subject Re: [PATCH] Allow mod_cache to be build/loaded as DSO
Date Tue, 07 Sep 2004 18:28:17 GMT
On Tue, 07 Sep 2004 11:14:46 -0700, Justin Erenkrantz
<> wrote:
> --On Tuesday, September 7, 2004 2:06 PM -0400 Jeff Trawick
> <> wrote:
> > Won't gcc 3.2+ have dynamic reference to instead of static
> > reference to libgcc.a?
> gcc 3.3 on Mac OS X and gcc 3.4.0 (stock) on Solaris both refer to libgcc.a.
> *shrug*

hrm...  we've had folks complain^H^H^H^H^H^H^H^Hnotice before that gcc
3.2 on Solaris referenced the .so and that if they copied
along with their Apache binaries it would run on another box

> > gcc < 3 will have static reference to libgcc.a too, but no
> > -print-libgcc-file-name option :(
> Well, not sure what we can do 'bout that.


> > Based on Joe's comment, this stuff depends on how gcc was built.
> It's better to try to figure this out than greatly obfuscate our code to
> work around a bug in one compiler.

agreed 100%; I'm just trying to understand what the pattern is, if
indeed there is one that can be instantiated in our configure logic

the alternative is something in a readme that tells how to build
Apache so that libgcc.a gets linked into DSOs automaticaly and/or what
it means if httpd or some module fails to load because
can't be found

View raw message