httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Trawick <traw...@gmail.com>
Subject Re: one remaining mpms-shared quirk
Date Sun, 15 Nov 2009 01:48:51 GMT
On Sat, Nov 14, 2009 at 8:10 PM, William A. Rowe Jr.
<wrowe@rowe-clan.net> wrote:
> ./configure with both --with-mpm=worker --enable-mpms-shared provides a really
> odd result;
>
> checking which MPM to use by default... worker
> ../httpd-2.x/configure: line 25999: server/mpm/event/modules.mk: No such file or directory
> checking for pthread_kill... yes
> ../httpd-2.x/configure: line 26148: server/mpm/prefork/modules.mk: No such file or directory
> ../httpd-2.x/configure: line 26197: server/mpm/simple/modules.mk: No such file or directory
> ../httpd-2.x/configure: line 26293: server/mpm/worker/modules.mk: No such file or directory
> checking for pthread_kill... (cached) yes
> mkdir modules/arch/unix
>
>
> Is this by design?  Should we use a different option to choose 'the mpm'
> for httpd.conf purposes?

I get different results with "--with-mpm=worker --enable-mpms-shared"...

checking which MPM to use by default... worker
configure: error: MPM yes does not support dynamic loading.
configure failed

The --enable-mpms-shared option handling doesn't deal with "yes"; it
expects "all" or a list of space-delimited MPMs.  I'll change it to
build the default MPM (--with-mpm) as shared when no argument is
passed on the --enable-mpms-shared option.  (and I guess
"no"/--disable... should do nothing, if it doesn't already)

Mime
View raw message