David Banning wrote:
>
> Well, I've installed FreeBSD fresh
> I installed midgard according to the Eddie Azman installation
> example.
That's not as up to date as it ought to be. Our fault.
> When firing up apache, I get the error;
>
> /www/bin/apachectl start
> Syntax error on line 4 of /www/conf/httpd.conf:
> Invalid command 'MidgardEngine', perhaps mis-spelled or defined by a module not
>included in the server configuration
> /www/bin/apachectl start: httpd could not be started
>
> I expected from this error that midgard is not installed.
> Which it does not seem to be;
>
> /www/bin/httpd -l
> Compiled-in modules:
> http_core.c
> mod_env.c
> mod_log_config.c
> mod_mime.c
> mod_negotiation.c
> mod_status.c
> mod_include.c
> mod_autoindex.c
> mod_dir.c
> mod_cgi.c
> mod_asis.c
> mod_imap.c
> mod_actions.c
> mod_userdir.c
> mod_alias.c
> mod_access.c
> mod_auth.c
> mod_so.c
> mod_setenvif.c
> suexec: disabled; invalid wrapper /www/bin/suexec
>
> however does it have to be? - going through my notes
> Emiliano wrote me:
>
> > > Well there's your problem: mod_so isn't compiled in, and mod_php3
> +is.
> > > You need to link in either mod_midgard or mod_so statically.
>
> which leads me to believe I only need one or the other. ?
You need mod_php3 and mod_midgard at runtime. These can be statically
compiled into apache, or you can load the as modules, but for that you
need mod_so (you do), which must of course be statically linked in
itself
or you'd have a bootstrapping problem.
Make sure that you have LoadModule and AddModule statements for midgard
and php3. The above error could mean that the Midgard module isn't
activated.
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]