> Not to worry. I won't come crying when it dies - I'll just flip back to
> 2.0. My site is not that big a risk - low traffic - and I'm running all
> cvs devel packages on it already. Note - this is my little site, _not_
> one of my clients'. I have always kept my site on the bleading edge so
> I
On Friday 02 April 2004 03:18 am, Geoffrey Young wrote:
> > Geoff, FYI -
> >
> > 'Patching' the APR_HAS_LARGE_FILES to 0 as described above did not work
> > for me. Even with it set to 0 in apr.h the server seg faulted. However,
> > using '--disable-lfs' DID work (and APR_HAS_LARGE_FILES did not ne
> Geoff, FYI -
>
> 'Patching' the APR_HAS_LARGE_FILES to 0 as described above did not work
> for me. Even with it set to 0 in apr.h the server seg faulted. However,
> using '--disable-lfs' DID work (and APR_HAS_LARGE_FILES did not need to be
> patched because it came out of the configure set to 0
On Thursday 01 April 2004 09:38 am, Geoffrey Young wrote:
> > Just wondering, is the older ( -D"2004-03-01" ) Apache2.1 still
> > available via CVS ( without you doing a lot of work )?
> >
> > If I could test against it, it would narrow my problem down.
>
> ok, it looks as though it's an fixable AP
On Thursday 01 April 2004 08:05 am, Stas Bekman wrote:
> Beau E. Cox wrote:
> > On Wednesday 31 March 2004 09:21 pm, Stas Bekman wrote:
> >>Beau E. Cox wrote:
> >>[...]
> >>
> >>>The module in question - mod_perl.c - line 614 is ' rcfg = '. I hand-
> >>>expanded the MP_dRCFG macro in the hope if ge
On Thursday 01 April 2004 09:38 am, Geoffrey Young wrote:
> > Just wondering, is the older ( -D"2004-03-01" ) Apache2.1 still
> > available via CVS ( without you doing a lot of work )?
> >
> > If I could test against it, it would narrow my problem down.
>
> ok, it looks as though it's an fixable AP
> Just wondering, is the older ( -D"2004-03-01" ) Apache2.1 still
> available via CVS ( without you doing a lot of work )?
>
> If I could test against it, it would narrow my problem down.
ok, it looks as though it's an fixable APR problem:
http://marc.theaimsgroup.com/?l=apache-modperl-dev&m=
Beau E. Cox wrote:
On Wednesday 31 March 2004 09:21 pm, Stas Bekman wrote:
Beau E. Cox wrote:
[...]
The module in question - mod_perl.c - line 614 is ' rcfg = '. I hand-
expanded the MP_dRCFG macro in the hope if getting more information,
but all that showed is, indeed, the routine was entered wi
Beau E. Cox wrote:
> On Wednesday 31 March 2004 02:49 pm, Geoffrey Young wrote:
>
>>>anway, I'm trying my best to track it down, as is philippe, but more eyes
>>>are always welcome. if you're looking for a place to start, I'd check
>>>out all the APR commits over the past two weeks - that is fi
On Wednesday 31 March 2004 02:49 pm, Geoffrey Young wrote:
> > anway, I'm trying my best to track it down, as is philippe, but more eyes
> > are always welcome. if you're looking for a place to start, I'd check
> > out all the APR commits over the past two weeks - that is first on my
> > list once
On Wednesday 31 March 2004 09:21 pm, Stas Bekman wrote:
> Beau E. Cox wrote:
> [...]
>
> > The module in question - mod_perl.c - line 614 is ' rcfg = '. I hand-
> > expanded the MP_dRCFG macro in the hope if getting more information,
> > but all that showed is, indeed, the routine was entered with
Beau E. Cox wrote:
[...]
The module in question - mod_perl.c - line 614 is ' rcfg = '. I hand-
expanded the MP_dRCFG macro in the hope if getting more information,
but all that showed is, indeed, the routine was entered with a non-NULL
request_rec:
A handy tip: you can make gdb open macros for you:
On Wednesday 31 March 2004 07:11 pm, Geoffrey Young wrote:
> Geoffrey Young wrote:
> >>anway, I'm trying my best to track it down, as is philippe, but more eyes
> >>are always welcome. if you're looking for a place to start, I'd check
> >> out all the APR commits over the past two weeks - that is
Geoffrey Young wrote:
>>anway, I'm trying my best to track it down, as is philippe, but more eyes
>>are always welcome. if you're looking for a place to start, I'd check out
>>all the APR commits over the past two weeks - that is first on my list once
>>I get a free moment.
>
>
> for those fol
> anway, I'm trying my best to track it down, as is philippe, but more eyes
> are always welcome. if you're looking for a place to start, I'd check out
> all the APR commits over the past two weeks - that is first on my list once
> I get a free moment.
for those following along, it definitely se
> I stand corrected. mod_auth_digest is alive and well in 2.1. I
> thought is was not because the mod_perl test was kicking in with
> another version.
:)
> NOW, I am testing mod_perl2 (cvs) with Apache2.1 - and -
> seg faults _everywhere_. Has anyone tried it yet (I know it is not
> supported ye
On Wednesday 31 March 2004 08:57 am, Geoffrey Young wrote:
> >>APACHE_TEST_HTTPD=/PATH/TO/HTTPD make test
> >>
> >>or
> >>
> >>t/TEST -httpd=/path/to/httpd
> >>
> >>etc. please refer to the documentation for more options.
> >
> > OK, I used option 1 above, however, it seems that the test suite
> >
>>APACHE_TEST_HTTPD=/PATH/TO/HTTPD make test
>>
>>or
>>
>>t/TEST -httpd=/path/to/httpd
>>
>>etc. please refer to the documentation for more options.
>
>
> OK, I used option 1 above, however, it seems that the test suite
> _insists_ on testing auth using mod_auth_digest.c (which is not ready
> ye
On Tuesday 30 March 2004 08:24 pm, Stas Bekman wrote:
> Beau E. Cox wrote:
> >> > How do I control how t/config/httpd.conf is setup?
> >>
> >>What seems to be the problem?
> >
> > Well, the t/config/httpd.conf generated somewhere in the mod_perl build -
> > I couldn't find it on first glance - is b
Beau E. Cox wrote:
> How do I control how t/config/httpd.conf is setup?
What seems to be the problem?
Well, the t/config/httpd.conf generated somewhere in the mod_perl build -
I couldn't find it on first glance - is based on the
Apache 2.0 configuration, NOT the Apache 2.1 configuration. I am
l
On Tuesday 30 March 2004 05:32 pm, Stas Bekman wrote:
> Beau E. Cox wrote:
> > Hi -
> >
> > I have 2 Apache2s on my test server:
> >
> > Apache 2.0.50-dev(cvs) installed in /home/test/usr/apache2
> >
> > and:
> >
> > Apache 2.1 (cvs) installed in /home/test/usr/apache2.1
>
> Apache 2.1 is not off
Beau E. Cox wrote:
> Hi -
>
> I have 2 Apache2s on my test server:
>
> Apache 2.0.50-dev(cvs) installed in /home/test/usr/apache2
>
> and:
>
> Apache 2.1 (cvs) installed in /home/test/usr/apache2.1
>
> When generating mod perl with:
>
> perl Makefile.PL MP_APXS=/home/test/use/apache2.1/s
Beau E. Cox wrote:
Hi -
I have 2 Apache2s on my test server:
Apache 2.0.50-dev(cvs) installed in /home/test/usr/apache2
and:
Apache 2.1 (cvs) installed in /home/test/usr/apache2.1
Apache 2.1 is not officially supported at the moment. If you want to play with
it you are on your own, Beau. Geo
Hi -
I have 2 Apache2s on my test server:
Apache 2.0.50-dev(cvs) installed in /home/test/usr/apache2
and:
Apache 2.1 (cvs) installed in /home/test/usr/apache2.1
When generating mod perl with:
perl Makefile.PL MP_APXS=/home/test/use/apache2.1/sbin/apxs
the test httpd.conf file is generated
24 matches
Mail list logo
