testing Apache:: modules with 5.8.0

please test that 5.8.0 has no problems with Apache:: modules on your platforms/configs. 5.8.0-RC1 is to be released in 2 days. I've reinstalled a bunch of Apache:: modules that I usually have with 5.8.0-tobe and all were installed fine but these two: Apache::SubProcess Apache::Module these tw

Re: DBI & win32 (was: question...)

On torsdag, maj 30, 2002, at 08:36 , Randy Kobes wrote: > > It would be very nice for the windows stuff - from what Doug > figured, the problem I was having building modperl2 on Win32 may > be related to something that has been fixed in perl-5.7.3. And so > if I make up modperl2 ppm packages bas

Re: DBI & win32 (was: question...)

On Thu, 30 May 2002, Gerald Richter wrote: > Hi Randy, > > > So I may package up my > > perl-5.7.3 build as a binary as well, to go along with > > an updated modperl-2 package ... > > > > Looks like it's time for 5.8.0 to be the official release... It would be very nice for the windows stuff - f

Re: DBI & win32 (was: question...)

Hi Randy, > So I may package up my > perl-5.7.3 build as a binary as well, to go along with > an updated modperl-2 package ... > Looks like it's time for 5.8.0 to be the official release... While we are talking about windows, do you have any experiences if DBI works under windows with mod_perl

Re: question...

On Wed, 29 May 2002, Doug MacEachern wrote: > On Wed, 29 May 2002, Fisher, James wrote: > > > I was testing the win32 build Apache2/Modperl2 available on Randy Kobes and > > I stumbled upon an odd behavior specific to Modperl2. I was merrily testing > > with the apache tool ab and it seems after

Re: question...

if you have msdev studio, try building modperl-2.0 from cvs which has a number of windows specific fixes. else, wait for 1.99_02 to be released (soonish). On Wed, 29 May 2002, Fisher, James wrote: > I was testing the win32 build Apache2/Modperl2 available on Randy Kobes and > I stumbled upon

Re: modperl-2.0 Apache::compat is not

On Wed, 29 May 2002, Herbert Rosmanith wrote: herbert, this is part of the reason modperl has not been released as '2.0' yet, but as 1.99_01 and upcoming 1.99_02. it is not 100% complete. we need input from people such as yourself to fill in the gaps, in particular with the compat mode. > I

moving 2.0's reminders/hints from Makefile.PL to the 'make install'stage

I think the following reminders: --- mod_perl dso library will be built as mod_perl.so You'll need to add the following to httpd.conf: LoadModule perl_module modules/mod_perl.so Apache Perl modules will be installed relative to Apache2/ Don't forget to: - configure 'PerlModule Apache2' in http

modperl-2.0 Apache::compat is not

hello, I have been struggling for two days to get a perl-module which I wrote under modperl-1 and apache-1.3.24. I am forced to switch to httpd-20 and modperl-2, since a particular configuration (with SSL and ) doesn't work with apache-1.3, but it will with httpd-2.0 Porting the module to modperl

Re: MP_INST_APACHE2 and man path

On Tue, 28 May 2002, Tatsuhiko Miyagawa wrote: > If I understand correctly, MP_INST_APACHE2=1 and "PerlModule Apache2" > is a workaround for co-existency of mod_perl 1.x and 2.x modules in > the same perl library path. (is it right?) ... > Installing /usr/local/bleadperl/man/man3/Apache::Test.3

Re: [Patch 1.3] $r->args(undef) doesn't work

On Wed, 29 May 2002, Geoffrey Young wrote: > below is a set of patches that adds tests for both $r->args(undef); (which uses > get_set_PVp via a one-hop from Perl-land) as well as $r->the_request(undef); (which >uses > get_set_PVp directly and which worked ok already). all tests pass for me wi

question...

I was testing the win32 build Apache2/Modperl2 available on Randy Kobes and I stumbled upon an odd behavior specific to Modperl2. I was merrily testing with the apache tool ab and it seems after hitting apache anywhere between 2-6 times with the command "ab -n 1000 http://127.0.0.1/hello";, or si

Re: [Patch 1.3] $r->args(undef) doesn't work

> So this: > > thing = (char*)((ST(1) == &sv_undef) ? NULL : pstrdup(p, SvPV(ST(1),na))) > > Probably intends to read: > > thing = (char*)((SvOK(ST(1))) ? pstrdup(p, SvPV(ST(1),na) : NULL) > cool! I integrated your new get_set_PVp logic and it worked just fine. nice work, and

follow-up: failed MODPERL-2 build on MacOSX (Apache/2.0.36mod_perl/1.99_02-dev Perl/v5.6.1)

doug, fyi, perl will not successfully complete a build on MacOSX *without* "undefined suppress" .. so modperl *will* pick it up in the compile flags . richard --On Tuesday, May 28, 2002 12:14 AM -0700 R Blake <[EMAIL PROTECTED]> wrote: > doug, > > i've made the change to '#if 0' in