AxKit porting troubles

2002-11-26 Thread Yuriy Syrota
Hello. I'm porting AxKit to apache2 & mod_perl2 and got strange following problem: Apache2 doesn't recognise AxKit's configuration directives though it loads the AxKit (I think so because apache2 calls AxKit per-server creation function). I tried to load AxKit.so by LoadModule (not LoadPerlModul

[patch] xs/APR/APR/Makefile.PL

2002-11-26 Thread Stas Bekman
As I have mentioned earlier here: http://mathforum.org/epigone/modperl-dev/thehplaldshend we need to adjust to the new way apr names the libs. Here is the patch that makes it work with the new way. Still need to handle correctly the previous way. Should this be integrated into ModPerl::MM? I have

Re: rfc: top level 2.0 CPAN modules naming

2002-11-26 Thread Doug MacEachern
On Tue, 26 Nov 2002, Stas Bekman wrote: > Doug MacEachern wrote: > > never intended the ModPerl:: namespace to be for third-party modules. > > why the change from Apache:: ? > > The idea came from ModPerl::Registry, I thought that's why it was > renamed from Apache::Registry in first place. no,

Re: [patch] xs/APR/APR/Makefile.PL

2002-11-26 Thread Doug MacEachern
of course, this apache "portable" runtime script does not work on windows. (tho, not sure if the existing Makefile.PL did either) strange thing is, MakeMaker should ignore libraries it cannot find, as it has been for me. APR.pm is only meant for using apr outside of modperl, which i don't think

Re: [patch] xs/APR/APR/Makefile.PL

2002-11-26 Thread Doug MacEachern
note that ap[ur]-config will be required, as there may be other libs such as -lgdbm. i've disabled the linking for the moment. i suppose if you patch was modified to enable only if -x $apr_config && -x $apu_config, that'd be ok. we just won't support older versions of apr or platforms that d

Re: rfc: top level 2.0 CPAN modules naming

2002-11-26 Thread Stas Bekman
Doug MacEachern wrote: On Tue, 26 Nov 2002, Stas Bekman wrote: Doug MacEachern wrote: never intended the ModPerl:: namespace to be for third-party modules. why the change from Apache:: ? The idea came from ModPerl::Registry, I thought that's why it was renamed from Apache::Registry in firs

Re: [patch] xs/APR/APR/Makefile.PL

2002-11-26 Thread Stas Bekman
Doug MacEachern wrote: note that ap[ur]-config will be required, as there may be other libs such as -lgdbm. i've disabled the linking for the moment. i suppose if you patch was modified to enable only if -x $apr_config && -x $apu_config, that'd be ok. we just won't support older versions of

Re: rfc: top level 2.0 CPAN modules naming

2002-11-26 Thread Doug MacEachern
On Wed, 27 Nov 2002, Stas Bekman wrote: > Doesn't Apache2 subdir solve the problem? All other modules with the > same name in 1.0 and 2.0 still have the same name. sort of. but the idea was to use the 1.x Apache::Registry with 1.99_xx. with Apache2.pm in effect, you'd get the new one, not the

Re: [patch] xs/APR/APR/Makefile.PL

2002-11-26 Thread Doug MacEachern
On Wed, 27 Nov 2002, Stas Bekman wrote: > are we good now? looks good to me. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

[Win32] mod_perl-1 and ActivePerl 8xx

2002-11-26 Thread Randy Kobes
ActivePerl, in their 8xx Win32 binaries based on perl-5.8, have enabled large_file support (a USE_LARGE_FILES compile-time flag). In compiling the cvs mod_perl-1 against this, however, there's an error in line 1963 of Apache.xs: statcache = r->finfo; about '=' relating incompatible types. If I