John Peacock wrote:
> I have this app that uses mason components that is known by multiple 
> different names, e.g. reports.[domainname].tld.  I have individual 
> reports-domain.conf files (since each has an independent IP address and 
> SSL configuration files).  It's all hunky dory.
> 
> Now I want to add non-ssl sites alongside these sites, basically with 
> the information needed to signup/get connected to the secure sites.  So 
> I copy my default Mason configuration files, so I can share all of the 
> existing Mason code (including my customized handler), edit the site 
> specific stuff, and restart apache and I get
> 
>       Can't locate Apache/Constants.pm...blah blah blah...compilation aborted 
> at /etc/httpd/vhosts.d/handler.pl...
> 
> even though neither the handler file nor the conf file in question 
> references Apache:::Constants at all!  I do have
> 
>       use Apache2::Const -compile => qw(:common);
> 
> in the handler, BTW.  If I rename the offending conf file, and change 
> nothing else, Apache happily starts up without a hitch.  I'm stumped.
> 
> I'm going to go about trying to create the minimum configuration 
> required to get mod_perl running for this conf file (since I don't 
> really need Mason), but it's making me crazy that I can't get this to 
> work...
> 

Are you referencing the Apache::Constants in the httpd.conf or any user 
conf files?

:Robert


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Mason-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mason-users

Reply via email to