On Monday 01 October 2001 05:42 pm, Aaron Bannert wrote: > On Mon, Oct 01, 2001 at 05:31:48PM -0700, Roy Fielding wrote: > > On Mon, Oct 01, 2001 at 04:59:20PM -0700, Aaron Bannert wrote: > > > I've been fooling around with this for the last week or so and I have > > > some more clues: > > > > > > - any module that is declared with APACHE_MODULE(.... most) while we > > > have --enable-mods-shared=most is properly build into a DSO. > > > > > > - if the module is declared with APACHE_MODULE(.... yes) then it > > > doesn't ever get the chance to become a DSO. The current workaround is > > > to explicitly declare --enable-foo=shared for each module that > > > currently defaults to static. > > > > 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 would have no problem using static in that macro to denote that a module must be compiled staticly. I would suggest actually reviewing all of the options to that macro. I am willing to bet that some of them are redundant. Ryan ______________________________________________________________ Ryan Bloom [EMAIL PROTECTED] Covalent Technologies [EMAIL PROTECTED] --------------------------------------------------------------
