httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Graham Leggett <minf...@sharp.fm>
Subject Re: [PATCH] AIX configure options
Date Wed, 08 Feb 2012 14:22:12 GMT
On 08 Feb 2012, at 4:08 PM, Michael Felt wrote:

> Well, it was building "something". I'll try the proposed change and make sure it is still
giving me "all" the mods.
> FYI - I have added --enable-ssl (so that the same script works for both 2.2.22 and 2.4.0
which have different ideas of "all".

v2.4.x and v2.2.x are subtly different to one another when it comes to MPMs - v2.2.x forced
you to choose a hard coded mpm at build time, while v2.4.x allows you to choose an mpm at
runtime in the same modular way that normal modules can be built.

How this affects you is that with v2.4.x things are easy, you add the "--enable-mpms-shared=all"
option and you're done. Each mpm is built as a module, administrator puts his preference in
a config file, done.

With v2.2.x, things are painful. The way RPM handled v2.2.x is that the build was executed
three times, each providing a version of httpd with one of the MPMs selected, creating three
separate binaries, /usr/sbin/httpd for prefork, /usr/sbin/httpd.worker for worker, and /usr/sbin/httpd.event
for event. The modules only needed to be built once, so the second and third builds excluded
all modules. Then there was a lot of scripted messing about to put everything in one tree
- painful.

Don't expect v2.4.x and v2.2.x to have the same script, it's very likely they won't have,
although the scripts may be almost identical.

It's up to you as to how much of v2.2.x you want to implement - you might choose to build
three packages with one mpm each, or try build one package with three separate httpd binaries
in it (like RPM did), or you might go "too much work for an old branch of httpd, focus efforts
on v2.4.x instead", which is also fine.

Regards,
Graham
--


Mime
View raw message