I 've already compiled Apache with DSO support. So what changes in the midgard compilation to do as you say? I guess I don't quite understand what you are advising here. I may be exposing my ignorance here, but I hate not understanding something, so let me ask some more questions:
1. I can recomile Apache to add mod's at any time, no? So as long as I've got Apache compiled with DSO I'm okay. 2. A standard configure --with-Apache, make, make install in mod_midgard makes it as a DSO, or does it? If not, how should one configure it to make a DSO object? 3. Then all I need to do is put in a few lines in httpd.conf and I'm all set? Am I missing something? On Sat, 03 Aug 2002 12:36:15 +0200, Emiliano <[EMAIL PROTECTED]> wrote : > Greg Bledsoe wrote: > > So would I actually be better off with a package file? Is that how the > > design of the Midgard compilation leans? > > Nope, not specifically. Most everyone I know compiles midgard as a dso, > which is what I was referring to. > > > I can do that - I'll uninstall > > current Apache and reinstall from .rpms, or start over on a fresh box. > > No need. But I would in fact suggest compiling apache separately but > with dso support (or go with the package if you prefer that -- it'll > have dso support), then load midgard dynamically at apache start. > > Emile > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
