On Monday 01 October 2001 06:16 pm, Aaron Bannert wrote:
> On Mon, Oct 01, 2001 at 05:42:13PM -0700, Aaron Bannert wrote:
> > > I thought that was by design -- "yes" means it must always be
> > > compiled-in.
> >
> > I don't know if it's really clearly defined anywhere, but I always took
> > "yes" to mean enable it, and --enable-mods-shared=most/yes to mean
> > "take all those enabled modules and make them shared".
> >
> > Would another setting of "static" be a good compromise? That
> > way mod_mime and mod_http can default to static even if you do
> > --enable-mods-shared=most/all, and then the others will become DSOs
> > if that same parameter is set.
>
> I have the fix in my tree now, but one thing still remains that is
> more to Roy's point: Now that some of these compiled-in modules are
> being built as modules, they aren't being loaded by default, and that
> means the default httpd.conf is failing. It's failing on thing like
> mod_access.
>
> Either we come up with a better httpd.conf (better detect default modules
> and add LoadModule lines) or we drop this patch altogether (meaning people
> will have to override the default set of static modules on a per-module
> basis with --enable-foo=shared).

We should fix the configure script so that it automatically adds the LoadModule
line, just like it did in 1.3.

Ryan
______________________________________________________________
Ryan Bloom                              [EMAIL PROTECTED]
Covalent Technologies                   [EMAIL PROTECTED]
--------------------------------------------------------------

Reply via email to