Derek Beattie wrote:
>
> I'm trying to install apache, ssl, and midgard from source and I have a couple
> of questions:
> 1. In the Monster Package is mod_ssl built as static or dynamic?
Static.
> 2. I see in the INSTALL.DSO instructions for apache a reference to mm libs for
> shared memory support. What happens if I don't use this?
Things will still work. SSL keeps state and shared information between
connections.
It can store this information in an dbm database (default) or shared
memory,
which is faster at the expense of memory of course.
> 3. On my attemp to build mod_ssl as a dynamic module. I'm using a variation of
> instruction out of the book Professional Apache. I do the following:
>
> -patch the extended API, without running apache's config script
> cd /usr/local/mod_ssl-2.6.2-1.3.12 --with-apache=/usr/local/src/apache_1.3.12
> --with-eapi
I must say I haven't tried this. Installing mod_ssl did the EAPI patch
for me.
> Yet, when I try and start apache I get a bunch of warnings for all of the
> modules it trys to load. Like, [warn] Loade DSO libexec/mod_header.so uses
> plain APache 1.3 API, this module might crash under EAPI! (please recompile it
> with -DEAPI)
>
> Do I simple need to change the --enable-rule=EAPI to DEAPI?
No, -DEAPI defines the symbol EAPI to the compilation environment.
Setting CFLAGS
to "-DEAPI" might work.
> I can keep trying to get it to work, I guess I just want to understand what's
> going on instead of using a RPM.
You don't have to use the RPM. In fact the MP is pretty bland,
feature-wise.
You could poke at the SPEC file of the MP RPM to get a start.
To be perfectly honest, the MP Spec file is just a basterdized version
of the
specfile I found on the mod_ssl pages.
Emile
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
