Re: PerlIOAPR_tell problem found

2001-12-17 Thread Doug MacEachern
On Tue, 18 Dec 2001, Stas Bekman wrote: > So shell we put your last temp patch in before we get this done, and > turn the todo sub-test normal? Or should we just get the ground ready > for Apache::PerlIO? can't just put the patch in since flags will be different on certain platforms. and for o

Re: PerlIOAPR_tell problem found

2001-12-17 Thread Stas Bekman
Doug MacEachern wrote: > On Tue, 18 Dec 2001, Stas Bekman wrote: > > correction from my last message: 4 bytes is a 32 bit int > > >>So is this a p5p call? >> > > i doubt p5p would go for it, but if you want to ask, go for it. I can I'll ask while following up on my bug report. > we ca

Re: PerlIOAPR_tell problem found

2001-12-17 Thread Doug MacEachern
On Tue, 18 Dec 2001, Stas Bekman wrote: correction from my last message: 4 bytes is a 32 bit int > So is this a p5p call? i doubt p5p would go for it, but if you want to ask, go for it. we can work around it, even for Apache::PerlIO. we can generate a modperl_largefile.h that defines the ripp

Re: PerlIOAPR_tell problem found

2001-12-17 Thread Stas Bekman
Doug MacEachern wrote: > the problem is that since we rip out largefile flags on the modperl side, > Off_t is 4 bytes (16 bit int), whereas on the perl side Off_t is 8 bytes > (64 bit int). for testing, add the largefile flags (as reported by > perl -V:ccflags_uselargefiles) like the diff below.

PerlIOAPR_tell problem found

2001-12-17 Thread Doug MacEachern
the problem is that since we rip out largefile flags on the modperl side, Off_t is 4 bytes (16 bit int), whereas on the perl side Off_t is 8 bytes (64 bit int). for testing, add the largefile flags (as reported by perl -V:ccflags_uselargefiles) like the diff below. we could solve this on the modp