A couple if people have had problems building mod_perl-1.27 on
Win32 because ModuleConfig.c wasn't generated (when no APACHE_SRC
was specified). John Petrakis <[EMAIL PROTECTED]> tracked this
down to $PERL_DIRECTIVE_HANDLERS in Makefile.PL not being defined
in this instance - the attached diff fix
On Tue, 10 Jul 2001, Randy Kobes wrote:
> thanks ... could I bother you for a couple more
> small changes? In enabling the Apache::src test,
> I didn't check properly that it would be skipped if
> mod_perl.so was built thru Visual Studio - this diff:
sure thing, that's in, thanks.
--
- Original Message -
From: "Doug MacEachern" <[EMAIL PROTECTED]>
To: "Randy Kobes" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, July 09, 2001 10:06 AM
Subject: Re: ModuleConfig on Win32
> On Mon, 9 Jul 2001, Randy Kobes wrote:
&g
On Mon, 9 Jul 2001, Randy Kobes wrote:
> Hi,
> I've attached a diff for Win32 against the current cvs
> mod_perl that does three things
cool, thanks randy, applied to cvs.
> I was looking at these because, first of all, wanting to see
> if ModuleConfig works on Win32, and also becau
Hi,
I've attached a diff for Win32 against the current cvs
mod_perl that does three things
- enables ModuleConfig on Win32: this required adding
the ModuleConfig.c to mod_perl.dsp, as well as adding
perl_call_handler and perl_get_startup_pool to mod_perl.def.
I tested this out w
