You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 9, 2024. It is now read-only.
I was provisioned a brand new (dv) instance at mediatemple. It is a CentOS 5.2 (final) OS. I have upgraded all yum packages and even have gotten mod_perlite to function properly.
But getting Movable Type running in this environment is tricky. It boils down to an apparent dependency upon Apache::Request - which is a mod_perl class. Is this true? Is mod_perl a dependency for mod_perlite applications? That doesn't seem right? Or is MT make a poor inference somewhere along the way and trying to route a request through a mod_perl layer because it can't detect CGI or mod_perlite?
Any clues?
The text was updated successfully, but these errors were encountered:
Indicating perhaps that by virtue of mod_perl being installed on the server, Movable Type will attempt to route requests through it. Or do I need to turn off mod_perl all together? or can i disable it for a single virtual host?
Just an fyi to anyone else setting this up. My Ubuntu box needed a bunch of stuff installed to get modperlite up and running.
apxs2 (via apache2-threaded-dev)
Perl dev (via libperl-dev)
Via CPAN, File::Which, Apache::TestMB, Apache::Test, Test-Simple and IPC::Run3
I also got a "random" warning during the compilation process (perl 5.10)
mod_perlite.c:329: warning: passing argument 2 of âPerl_sys_init3â from incompatible pointer type
/usr/lib/perl/5.10/CORE/proto.h:4696: note: expected âchar **â but argument is of type âchar * ()[2]â
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I was provisioned a brand new (dv) instance at mediatemple. It is a CentOS 5.2 (final) OS. I have upgraded all yum packages and even have gotten mod_perlite to function properly.
But getting Movable Type running in this environment is tricky. It boils down to an apparent dependency upon Apache::Request - which is a mod_perl class. Is this true? Is mod_perl a dependency for mod_perlite applications? That doesn't seem right? Or is MT make a poor inference somewhere along the way and trying to route a request through a mod_perl layer because it can't detect CGI or mod_perlite?
Any clues?
The text was updated successfully, but these errors were encountered: