On Tue, 4 Jun 2002, Matt Sergeant wrote:
> OK, I'm applying the following diff. Does it make sense to you? (I'm
> completely lost as to why I need to do this, so any guidance is most
> welcome!)
looks right to me. same issues that have been plaguing modperl itself
ever since 5.6.0 was relea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 04 June 2002 12:25 am, Doug MacEachern wrote:
> On Tue, 4 Jun 2002, Matt Sergeant wrote:
> > Seems to be I think - but then this isn't a bug I've been able to
> > replicate. I asked the person to try recompiling with an explicit -DEAPI
> >
On Tue, 4 Jun 2002, Matt Sergeant wrote:
> Seems to be I think - but then this isn't a bug I've been able to replicate. I
> asked the person to try recompiling with an explicit -DEAPI and it made no
> difference. AxKit uses Apache::src to get the headers and CFLAGS.
>
> Does the request_rec c
On Mon, 3 Jun 2002, Matt Sergeant wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Sorry for the off topic post, but I'm not sure where else to post...
>
> Has anyone here ever seen "bugs" with requests on an EAPI enabled Apache where
> r->per_dir_config is NULL? I haven't managed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry for the off topic post, but I'm not sure where else to post...
Has anyone here ever seen "bugs" with requests on an EAPI enabled Apache where
r->per_dir_config is NULL? I haven't managed to replicate the bug yet, but a
number of AxKit users a
