You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Peter Brown <re...@users.sourceforge.net> on 2001/04/05 18:17:02 UTC
enable-modules=most and enable-shared=max
hi all
just a query
in previous versions of apache the configure options
enable-modules=most and enable-shared=max used to enable most modules
and set shared for all modules
i have tried these options with apache 2.0
and they dont seem to do what they used to do
is there any intension of putting these back in configure ??
-------------------------------------------------------------------------
Peter Brown
Web Programmer/Sys Admin/Apache Admin Education Development Web
peter@edw.com.au www.edw.com.au
-------------------------------------------------------------------------
Re: enable-modules=most and enable-shared=max
Posted by Danek Duvall <dd...@eng.sun.com>.
I didn't ask the original question, but I've been trying for the same goal.
It seems that --enable-shared=max simply isn't supported, and that
--enable-mods-shared is the new flag. And it doesn't take 'max', but
'most' or 'all' like --enable-modules.
However, it seems that the only modules that actually get compiled as
shared modules are the ones which are declared with the 'default' argument
in APACHE_MODULE() set to 'most'. If it's set to 'yes', then it gets
compiled statically into httpd.
The quick fix would be to enable 'yes' to allow a shared module, but there
will be a few (like mod_so) that can't be shared. So it's a bit more
complicated than that.
This is both with 2.0.16 and one of today's CVS snapshots.
Has anyone fixed this yet, or should I try for a fix?
Thanks,
Danek
Re: enable-modules=most and enable-shared=max
Posted by Greg Ames <gr...@remulak.net>.
Peter Brown wrote:
>
> hi all
> just a query
> in previous versions of apache the configure options
> enable-modules=most and enable-shared=max used to enable most modules
> and set shared for all modules
> i have tried these options with apache 2.0
> and they dont seem to do what they used to do
>
> is there any intension of putting these back in configure ??
>
A quick peek at my ./configure shows:
-------------------------------------------------------
if test "${enable_modules+set}" = set; then
enableval="$enable_modules"
for i in $enableval; do
if test "$i" = "all" -o "$i" = "most"; then
module_selection=$i
else
eval "enable_$i=yes"
fi
done
fi
--------------------------------------------------------
What symptoms are you seeing?
Greg