> Now this doesn't solve your problem. You want the env to be set in
> filters. We need to spec how this should work first. Doug?
Thanks for the explaination.
I had a feeling it was due to some sort of buffering, but I thought the
error was when I didn't get the environment, rather than when I a
Andreas J. Koenig wrote:
>>On Fri, 02 Aug 2002 14:21:23 +0800, Stas Bekman <[EMAIL PROTECTED]> said:
>
>
> > Then it should link to:
> > http://perl.apache.org/products/apache-modules.html
>
> > Who's in power to change that?
>
> I'd suggest you generate a short HTML page that con
Doug MacEachern wrote:
> +1 on removing it.
I've removed it from the code, but it'll be still automatically picked
by source scan and therefore regenerated in:
./src/modules/perl/modperl_constants.c
./xs/ModPerl/Const/modperl_constants.c
./xs/tables/current/Apache/ConstantsTable.pm
Do we have
On Mon, 12 Aug 2002, Stas Bekman wrote:
> it failed to create the wrapper because the API included an 'int *'
> arg, whose typemap was undefined. Is it safe to use 'int * | PTR'
> typemap? I've checked the conversion functions and they seem to do the
> right thing:
that's fine for the typemap.
On Wed, 14 Aug 2002, Stas Bekman wrote:
> I was always building with MP_APXS. Now if I try using MP_AP_PREFIX
> pointing to the httpd-2.0 source tree there are all sort of problems. Am
> I the only one seeing them?
haven't tried pointing it at a source tree in a while.
what's wrong with point
On Wed, 14 Aug 2002, Stas Bekman wrote:
> Do we have some magic in the source scannig code to tell it to skip that
> macro?
$Apache::ParseSource::defines_unwanted
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional com
Doug MacEachern wrote:
> On Wed, 14 Aug 2002, Stas Bekman wrote:
>
>
>>I was always building with MP_APXS. Now if I try using MP_AP_PREFIX
>>pointing to the httpd-2.0 source tree there are all sort of problems. Am
>>I the only one seeing them?
>
>
> haven't tried pointing it at a source tre
On Mon, 12 Aug 2002, Goehring, Chuck Mr., RCI - San Diego wrote:
> Randy,
>
> I'm using Perl 5.6.0 for this. Should I be using 5.8.0? Does
> that affect ModuleConfig.c?
>
> Having problems running things with the version I put out last
> week. It complains about the dumbest things and is over
