duh...now that i've had some more coffee...the line:
PerlVersionINC On
must come before the PerlINC statement. PerlINC wont store that path
unless PerlVersionINC is On.
dave
On Mon, 31 Jul 2000, Dave Moore wrote:
> you arent doing anything wrong. you probably just need to upgrade to the
> latest version of Apache::ExtUtils. this is not the same ExtUtils that
> comes with mod_perl 1.24. you will have to get it from the latest cvs
> snapshot of mod_perl. you will also have to remake/install PerlVINC after
> you install ExtUtils. see if that helps.
>
> On Sat, 29 Jul 2000, Patrick wrote:
>
> > Hi all,
> >
> > (debian potato)
> > apache-ssl : 1.3.9.13-2
> > modperl : 1.21.20000309-1
> > perl : 5.005
> > Apache::PerlVINC : 0.01 compiled by myself
> >
> > As recommended in the guide, i'm trying to use Apache::PerlVINC since
> > I have 3 virtualhosts, and the same sets of modules for all three (same
>namespace), in
> > three separate directories (one production, two developpments).
> >
> > So I have in httpd.conf
> >
> > PerlModule Apache::PerlVINC
> > PerlINC /opt/anciens/membres
> > PerlVersionINC On
> > PerlFixupHandler Apache::PerlVINC
> >
> > But as soon as I put these 4 lines, apache doesn't run anymore.
> > An strace at start-up shows at the end :
> >
......some stuff was here.......
> >
> > It seems not to be happy not to found DESTROY.al, but after that i'm
> > lost.
> > What am I doing wrong ? How can I correct ? Is there another
> > possibility to achieve the same goal ?
> > (besides running different copies of Apache binded on different ports)
> >
> > If that's make a difference i'm also using Apache::StatINC
> >
> > Thanks in advance for your time and your answers.
> >
> > PS: modperl just rocks, kudos to everyone !
> >
> > --
> > Patrick.
> > Because if life has a meaning, we should already know it.
> >
--
Dave Moore
Web Application Developer
mailto:[EMAIL PROTECTED]
ePALS Classroom Exchange
http://www.epals.com/
Connecting more than 1.9 million students and teachers in 182 countries!
