David Banning wrote:
> > That's because apxs is supposed to take care of that. To compile in
> > mod_midgard statically, use the
> > --activate-module=/path/to/mod_midgard.c switch to apaches' configure
> > command.
>
> ./configure --prefix=/www --activate-module=src/modules/php3/libphp3.a \
> --activate-module=/usr/David/midmod/mod_midgard-1.2.5/mod_midgard.c
>
> gets me:
>
> Configuring for Apache, Version 1.3.12
> + using installation path layout: Apache (config.layout)
> + activated php3 module (modules/php3/libphp3.a)
> configure:Error: Module source already has to be below src/modules/ to
> be activated
>
> I don't know what that means. So I tried your second suggestion;
Sorry, that should have been
--add-module=/usr/David/midmod/mod_midgard-1.2.5/mod_midgard.c
Midgard-php replaces php3 (it's a superset of php3), so you'll need to
use that instead of --activate-module=src/modules/php3/libphp3.a
> > To build load mod_midgard dynamically, use the
> > --enable-module=so to apaches' configure command and after compiling
> > and installing apache, reconfigure & rebuild mod_midgard.
>
> That got it compiled and installed, but /www/bin/httpd -l shows;
>
> # /www/bin/httpd -l
> Compiled-in modules:
> http_core.c
> mod_so.c
> mod_php3.c
> suexec: disabled; invalid wrapper /www/bin/suexec
>
> which is at least showing mod_so there, but the error is still at the
> bottom.
Which error?
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]
