David R Newman wrote:
> > > If PHP has really made it that difficult, match versions: Midgard 1.4.1
> > > for PHP 4.0.4pl1, Midgard 1.4.2 for PHP 4.0.5 and so on.
> >
> > I'd rather not. I'm using PHP from debian packages, I'd not want to be
> > stuck with an older version Midgard.
>
> Except that most distributions are sticking to 4.0.4pl1. Not even Mandrake
> Cooker has produced a PHP 4.0.5. They no doubt came across the same
> problems as you're fighting, and decided to stick with the devil they know.
I've no issues at all with having 404pl1-compatible code in CVS, and
having to fix things by hand for my own situation.
> Changing them all back to AC_ instead of PHP_, *after* installing
> automake made everything compile.
Whoohoo. What fun. But having AC_ there in the first place doesn't
work?
> But I still can't get Apache to start with Midgard, or give me a
> sensible error message.
>
> Is there are particular order for loading the modules in httpd.conf?
> Should Midgard be before PHP or vice versa? Does there have
Someone reported having to have load mod_midgard first. I personally
haven't encountered that.
> to be a ClearModuleList after loading these modules but before
> adding them?
Nope.
IIRC you were using binary modules from HKLC? Please try compiling
from source. If that still bombs out, running apache under gdb could
help us pinpoint your problem. See
http://www.midgard-project.org/article/1096.html (although you don't
need to have fresh, from-source installations of mysql and apache,
just the midgard components).
Emile
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
