Stas Bekman wrote:
> [EMAIL PROTECTED] wrote:
>
>>stas2004/04/28 14:29:39
>>
>> Modified:t/conf modperl_extra.pl
>> Log:
>> - log the reason for the last change:
>>http://rt.perl.org:80/rt3/Ticket/Display.html?id=29018
>> - tidy up a bit
>>
>> Revision ChangesPath
>
[EMAIL PROTECTED] wrote:
stas2004/04/28 14:29:39
Modified:t/conf modperl_extra.pl
Log:
- log the reason for the last change:
http://rt.perl.org:80/rt3/Ticket/Display.html?id=29018
- tidy up a bit
Revision ChangesPath
1.46 +10 -4 modperl-2.0/t/conf/mod
> Basically, we want to define MODPERL2 as a server define, and the only phase
> where you can safely do that before configuration is during the hook-registry
> phase. the pre_config hook is not early enough for this.
why isn't pre_config early enough? because of the ap_read_config call?
>
> B
Philippe M. Chiasson wrote:
Stas Bekman wrote:
Philippe M. Chiasson wrote:
It's been a long awaited feature, to bring back something similar to the old
mod_perl option to have mod_perl statically linked to httpd. Here is my attempt
at it.
You rock, this looks so simple :)
The original way I
Philippe M. Chiasson wrote:
Geoffrey Young wrote:
There is currently one bug with mod_perl compiled statically. It tries to add
the MODPERL2 server define at hook-registry phase, but for statically linked
modules, that hook-registry phase is called before ap_server_config_defines is
created.
hmm
Unfortunately I've to drop this idea, since when you want to do IO with
controlled timeout you should be able to get the TIMEUP events trappable. So
I'll just leave things as they are now :( We may add the simple API later,
even if through a 3rd party module...
_
Stas Bekman wrote:
> Philippe M. Chiasson wrote:
>
>>It's been a long awaited feature, to bring back something similar to the old
>>mod_perl option to have mod_perl statically linked to httpd. Here is my attempt
>>at it.
>
>
> You rock, this looks so simple :)
>
>
>>The original way I attemp
Geoffrey Young wrote:
>
> Philippe M. Chiasson wrote:
>
>>It's been a long awaited feature, to bring back something similar to the old
>>mod_perl option to have mod_perl statically linked to httpd. Here is my attempt
>>at it.
>
>
> whee!
This patch sure needs a bit of polishing, but yes, it
On Wednesday 28 April 2004 02:09 am, Geoffrey Young wrote:
> It looks like 2.1 is going through a big update tonight,
> and the cvs sources are unstable.
>
> If you have a chance, can you let me know when it is
> usable again?
>
> my nightly build last night went off without a
It looks like 2.1 is going through a big update tonight,
and the cvs sources are unstable.
If you have a chance, can you let me know when it is
usable again?
my nightly build last night went off without a hitch:
/apache/2.1/worker/perl-5.8.4/bin/httpd -d
/src/mod_perl-2.0/Mo
Carl Brewer wrote:
Stas Bekman wrote:
Hmm, strange. And if you run any other test it succeeds?
make test seems ok except for these :
Failed Test Stat Wstat Total Fail Failed List of Failed
---
t/apr
Stas Bekman wrote:
Hmm, strange. And if you run any other test it succeeds?
make test seems ok except for these :
Failed Test Stat Wstat Total Fail Failed List of Failed
---
t/apr-ext/uuid.t
Carl Brewer wrote:
Stas Bekman wrote:
yes, please submit a verbose run's output only for:
t/TEST -v t/apr-ext/uuid.t
It's not finding perlloadmodule5.pm, but the file exists :
/data/src/modperl-2.0/t/response/TestDirective/perlloadmodule5.pm
Looks like a syntax error in httpd.conf, the line
13 matches
Mail list logo
