>>My guess is you are using relative paths and when using ASP
>>you have a different "current directory" than when using CGI.


I know - that's quite logical - but the remedy (absolute path) doesn't work.

I have tried to use both absolute and relative paths. I tried to set
absolute path via $ENV and use lib - this doesn't help either. Perl seems to
be searching in its own install directory for SWISH::ParseQuery.

Note that the use lib path whish is set at install (in swish.cgi) doesn't
work at all - via cgi or ASP.


Zeeshan Ahmad,
FMC Computing Services


-----Original Message-----
From: Bill Moseley [mailto:moseley@hank.org] 
Sent: Friday, 12 December 2003 5:00 PM
To: Ahmad, Zeeshan (FMC)
Cc: Multiple recipients of list
Subject: Re: [Ignor Abuse] RE: [SWISH-E] Re: [XWarn] RE: Re: Fixing Swish
2.4.0 To Work on W

On Fri, Dec 12, 2003 at 04:05:38PM +1030, Ahmad, Zeeshan (FMC) wrote:
> Another perl script problem on Windows.

(or is it the other way around?)


> 
> Swish.cgi works fine when called directly from web browser (use lib qw
> (./lib))

All depends on what the web server is using for the current directory.

> When I run it, Perl can't locate SWISH::ParseQuery.pm (not found in @INC
> stuff). I tried different use lib settings (including original) but of no
> avail.

Are you using absolute paths?


> 
> If I change 
> 'use SWISH::ParseQuery' to 
> 'use lib qw (E:/Program
Files/swish-e/lib/swish-e/perl/SWISH/ParseQuery.pm)', it works. Note this is
> my installed path.

No way.  use lib is a set of strings pre-pended to the module name.  You
can use a complete path to the file in a use lib statement.

  perldoc -f use
  perldod -f require (not use of $prefix in that example)


> 
> Then I would need to fix TemplateDefault location etc. similarly...what a
> pain. I think it's a Perl engine issue.

Unlikely.  My guess is you are using relative paths and when using ASP
you have a differert "current directory" than when using CGI.

-- 
Bill Moseley
moseley@hank.org