Not for me.  I hit the pwd issue early on in my (currently incredibly
frustrating and dubious-to-the-point-of-abandonment) migration to Apache
2.2. 

It doesn't sound like that's Jeff's problem either; he says that the
routines can't be found, not the file.

E

> -----Original Message-----
> From: Clinton Gormley [mailto:[EMAIL PROTECTED] 
> Sent: Friday, August 29, 2008 11:19 AM
> To: Berg, Eric
> Cc: Sean Davis; Jeff Pang; modperl perl apache org
> Subject: RE: a require problem
> 
> Is this not a current-working-directory issue?
> 
> This isn't terribly well documented on the mod_perl site, but from 
> http://perl.apache.org/docs/2.0/api/ModPerl/Registry.html
> 
> 
>         META: document that for now we don't chdir() into the script's
>         dir, because it affects the whole process under threads.
>         ModPerl::RegistryPrefork should be used by those who run only
>         under prefork MPM.
>         
> Try using absolute paths for 'use lib', instead of : use lib './lib' 
> 
> clint
> 
> On Fri, 2008-08-29 at 10:53 -0400, Berg, Eric wrote:
> > Jeff,
> > 
> > I'm running into issues with mod_perl2 that sound like they may be
> > related.  Are you, in fact, running this script under 
> > mod_perl?  Doesthe
> > myttt.tmpl file that you refer to contain Perl code that is to be
> > eval'ed in your myscr.pl?
> > 
> > Just yesterday I ran into a problem in which using do( 
> > $file ) or eval($file ) both had problems in that they did 
> > not successfully execute the code in $file.
> > 
> > Does that sound like your problem?
> > 
> > Folks, is there some kind of setting for mod_perl2 that affects
this, or
> > a different way to accomplish this?
> > 
> > Eric
> > 
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On 
> > > Behalf Of Sean Davis
> > > Sent: Friday, August 29, 2008 10:05 AM
> > > To: Jeff Pang
> > > Cc: modperl perl apache org
> > > Subject: Re: a require problem
> > > 
> > > On Fri, Aug 29, 2008 at 9:54 AM, Jeff Pang 
> <[EMAIL PROTECTED]> wrote:
> > > > I have began a project, but meet some problems,:)
> > > >
> > > > say there are three dirs:
> > > >
> > > > |- cgi-bin
> > > > |- cgi-bin - lib
> > > > |- cgi-bin - template
> > > >
> > > >
> > > > I have a script in cgi-bin, which requires the template 
> > > file from template
> > > > dir.
> > > > This script also uses a library file (.pm) from lib dir.
> > > > Finally the library need to require the former template 
> file too.
> > > >
> > > > say the script is myscr.pl, the lib file is mylib.pm, the 
> > > template file is
> > > > myttt.tmpl.
> > > >
> > > > so in myscr.pl:
> > > >
> > > > use lib './lib';
> > > > use mylib;
> > > > require 'template/myttt.tmpl';
> > > >
> > > >
> > > > in mylib.pm:
> > > >
> > > > require '../template/myttt.tmpl';
> > > >
> > > >
> > > > When I execute "perl mysrc.pl", it can't run, saying 
> the routines in
> > > > myttt.tmpl can't be found.
> > > 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
- - - -

This message is intended only for the personal and confidential use of the 
designated recipient(s) named above.  If you are not the intended recipient of 
this message you are hereby notified that any review, dissemination, 
distribution or copying of this message is strictly prohibited.  This 
communication is for information purposes only and should not be regarded as an 
offer to sell or as a solicitation of an offer to buy any financial product, an 
official confirmation of any transaction, or as an official statement of Lehman 
Brothers.  Email transmission cannot be guaranteed to be secure or error-free.  
Therefore, we do not represent that this information is complete or accurate 
and it should not be relied upon as such.  All information is subject to change 
without notice.

--------
IRS Circular 230 Disclosure:
Please be advised that any discussion of U.S. tax matters contained within this 
communication (including any attachments) is not intended or written to be used 
and cannot be used for the purpose of (i) avoiding U.S. tax related penalties 
or (ii) promoting, marketing or recommending to another party any transaction 
or matter addressed herein.

Reply via email to