Colin Wetherbee wrote:
Greetings.

Following reading Stas's last email to Scot, I poked around on the
configuration directives page and saw that PerlSwitches -I/foo is a
convenient replacement for 'use lib'.

I removed 'use lib' from a script and put the following in my virtual host
section:

PerlSwitches -I/var/www/hydrogen.denterprises.org/exec/perl

This doesn't appear to end up in @INC because I get the following in my
error log (which shows that /var/www/... is not in @INC):

[Fri Oct 15 21:23:33 2004] [error] 20945: ModPerl::Registry: Can't locate
Hydrogen/Const.pm in @INC (@INC contains: /usr/lib/perl5/Apache2 /etc/perl
/usr/local/lib/perl/5.8.4 /usr/local/share/perl/5.8.4 /usr/lib/perl5
/usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8
/usr/local/lib/site_perl . /etc/apache2/ /etc/apache2/lib/perl) at
/var/www/suexec/hydrogen.denterprises.org/hydrogen.pl line 21.\nBEGIN
failed--compilation aborted at
/var/www/suexec/hydrogen.denterprises.org/hydrogen.pl line 21.\n

Was the request made to that vhost. I'm sure it works if you move it out of the <virtualhost> container. May be that path is wrong and perl has ignored it? Does the following test work?


perl -I/var/www/hydrogen.denterprises.org/exec/perl -MHydrogen::Const -e0

Is PerlSwitches functionality still experimental?

Not at all.

Probably unrelated but judging by the error message it seems that you are using an old mod_perl version (in your bug reports please always follow these guidelines):
http://perl.apache.org/docs/2.0/user/help/help.html#Reporting_Problems


--
__________________________________________________________________
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

--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html



Reply via email to