I'm also running a Mason based system, but I'm sticking with mod_perl-1.0 for now. From the Mason FAQ: (http://www.masonhq.com/docs/faq/#can_i_use_mason_with_mod_perl_1_)

Until some time after mod_perl 2.0 is officially released, Mason will only support mod_perl 1.x, specifically 1.22+.

You may be able to use Mason with mod_perl 2.0 if you turn on mod_perl 2.0's 1.x compatibility layer by loading ``Apache::compat'' before you load Mason.

Hope this helps

Casey Songer
[EMAIL PROTECTED]


Stas Bekman wrote:

Issac Goldstand wrote:

Forwarding this from another list, because it's more appropriate here :-)
----- Original Message -----
*From:* Ron Gidron <mailto:[EMAIL PROTECTED]>
*Sent:* Monday, February 10, 2003 3:48 PM
*Subject:* [Perl] how to static link mod_perl 2 into apache 2.0

I am trying to install a Mason based system.
This package requires mod_perl statically linked and not as a DSO. for this new installation I decided to test Apache 2.0 and mod_perl 2.0.
I downloaded the source for both packages and I am able to configure and make / make test /make install for both without problems however
when I issue the command "apachectl -l" I don't see any reference to mod_perl. I have tried playing with the ./configure options for apache (--enable-perl etc) but nothing seams to get me to where I need to go, this is getting quite frustrating... does anyone have any tips?
have any of you installed this configuration before, do you happen to remember the order of steps you took?

At this point only DSO is supported by 2.0. What's wrong with using DSO? The package requires mod_perl to be statically linked, but it talks about mod_perl-1.0. I'd first check with Mason folks whether 2.0 is supported at all.

__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com


Reply via email to