* Randy Kobes ([EMAIL PROTECTED]) [010304 19:05]:
> Hi,
>     This is probably due to an incompatibility between 
> apache/mod_perl versions - note also that, as of mod_perl-1.25,
> the mod_perl dll that is placed in your /Apache/modules
> directory is now named mod_perl.so, to agree with the new
> apache convention (this dll should be offered to be installed
> with the mod_perl ppm install).

Yes, it the .so was put in the right place. But when using
Apache::Request (with the non-dev libapreq), Dynaloader in mod_perl.pm
still demanded that ApacheModulePerl.dll be there.

>    I've placed at 
>     http://theoryx5.uwinnipeg.ca/ppmpackages/libapreq-dev.ppd
> a ppm package of (the development version of) libapreq - this was
> built against mod_perl-1.25/apache_1.3.19, so should probably
> work with your set-up. If you want to try building this for
> yourself with VC++, you'll need the cvs version of libapreq - links 
> to this are available at http://perl.apache.org/.

I'm using mod_perl 1.25 (from the -1.3.19 PPD) and apache 1.3.19, but
when I try to startup something that uses Apache::Cookie, I get:

---------------
Apache.exe: Entry Point Not Found

  The procedure entry point hvrv2table could not be found in the
  dynamic link library mod_perl.so
---------------

I've worked around the cookie problem in my application by making each
cookie implementation its own class and switching to CGI::Cookie for
the Win32 implementation. (This is a good thing on its own, so there
*is* always a silver lining :-) So I'm not in a huge rush anymore to
get this up and running. I *am* curious though and will try and help
out as much as I can. Maybe even learn something in the process...

Thanks,

Chris

-- 
Chris Winters ([EMAIL PROTECTED])
Building enterprise-capable snack solutions since 1988.

Reply via email to