Yup, I did the ./configure --help | more as well and got the impression I
would need to enable the modules one by one....is that true? It seems like
the Midgard installation directives suggest a short cut but I have not
gotten it to work....the sense I cone from the config help was that I would
have to enable all the modules I wanted at least those which were not
default modules, and then enable them ALL shared....one at a time....there
weren't many that I wanted to add that were not in the default set, mod_so,
mod_ssl and mod_log_agent...but then to have to go back and explicitly make
each one of the whole set shared seems...uh...inefficient, inelegant....you
get my drift....are there alternatives?
kp
> -----Original Message-----
> From: Hepworth United [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, February 03, 2001 4:23 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [midgard-user] Apache question....
>
>
> The instructions are not clear, are they?
>
> $ ./configure --help | more
>
> will list the valid directives you can use when configuring
> apache. It also
> shows you which core modules are enabled by default and which are
> disabled.
>
> Assuming you have compiled and installed mod_ssl (or whatever), you will
> find a file called mod_ssl.c in apache's src/modules/extra directory.
>
> All you should need to do then (from the top level of apache) is:
>
> $ ./configure --enable-module=ssl
>
> If you need to change the apache config regularly, you could think about
> compiling apache with all its modules shared:
>
> ./configure \
> --enable-module=so \
> --enable-shared=ssl \
> --enable-shared=env \
> --enable-shared=log_config ... and so on, listing all the modules
> you think
> you will ever need.
>
> Then you use httpd.conf to specify which modules to load at runtime.
> (Instructions in the file). This avoids having to recompile every time you
> want to change the config; the downside is that the conf file is more
> complex and apache takes slightly longer to load up when you start it.
>
> See dso.html in your documentation.
>
> Jon
>
> Jon Armitage
> [EMAIL PROTECTED]
> http://www.hepworthunited.co.uk
>
> ----- Original Message -----
> From: "Ken Pooley" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, February 02, 2001 2:34 PM
> Subject: [midgard-user] Apache question....
>
>
> > I am working on a fresh install of apache from source files...I
> am trying
> to
> > follow the directions from our install but I am running into a
> problem...it
> > seems to be....with the line
> > --enable-module=all
> > when I run the configure, then MAKE I get an error that says
> > **** No rule to make target 'all'. Stop
> > then a
> > ***[build-std] Error 2
> >
> > Obviously if I omit the
> >
> > --enable-module=all
> >
> > then when I thy to make the certificate then it says I needed to
> > have --enable-mod_ssl
> >
> >
> > ....My other question is sort of obvious but I want to make sure....if I
> > compile Apache with ssl in and then recompile later...do I still need to
> > explicitly recompile ssl in again...I am guessing yes but I want to make
> > sure there is not a loophole I don't know about.....
> >
> > kp
>
>
>
> ---------------------------------------------------------------------
> 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]
