httpd-apreq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bojan Smojver <>
Subject Re: [PATCH]: Enable static build of APREQ 2
Date Mon, 06 Oct 2003 04:06:30 GMT
On Mon, 2003-10-06 at 11:47, Joe Schaefer wrote:

> Looks great so far!  I haven't tried running it yet, but I'm wondering
> about the apxs dependence in the patch.  Doesn't apxs depend on mod_so
> being installed?  Does the preinstalled httpd need to have a working apxs?  

Not sure and yes. This can, of course, be avoided by having more options
given to the configure script about where the relevant directories are.
I just thought that there aren't many people without APXS out there.

> If not, where should/does wind up after installation?

Well, since APXS has to be there, if it isn't found, nothing happens at
all (i.e. configure fails). If you don't specify --disable-shared, will end up in the library directory of Apache 2 and it'll
be most likely used to link against when httpd is build, rather than
libapreq.a (gcc normally prefers shared libs). Don't see any harm in

> Also, since we can get the apache srcdir from `apxs -q abs_srcdir`, if
> we're going to require a working apxs, maybe we should just do something
> with "--with-apache2-apxs=... --disable-shared" instead of adding
> another configure option (and distinguish between shared/static libapreq
> and shared/static mod_apreq).

That's a possibility as well. I actually did the --with-apache2 on
purpose - it enables static linking by explicitly setting the root of
the source tree of Apache. But that is not the only way to go about it.

> Another possibility is to do something clever with httpd's 
> --with-module=... option, but I'm not smart enough to get a full
> compile out of it.

Not sure about this. Never used it.

> Maybe a small step in this direction would 
> be to move httpd-apreq-2/src/* over to httpd-2.0/srclib/apreq
> and figure out how to get *that* to compile libapreq.

That's not difficult to do. All you need to do is fiddle with config.m4
file from the patch and specify which files are dependencies of (looking at one of Apache supplied config.m4 files is an
excellent start). Then Apache build system does the rest. With Apache,
there is more than one way to skin the cat ;-)

> If I'm jumping the gun by asking such questions before trying the
> patch, just holler.

Nah, it's better that you include something you like than nothing at
all. For all it matters, you could just have a config.m4 file, Apache's and then a few sentences in README on how it's done (i.e.
copy files X, Y, Z to Apache source tree, run ./buildconf etc.)


View raw message