On Wed, 27 Dec 2000, Daniel Jacobowitz wrote:
I assume that if Apache is built with LFS, we do need them (though I
think apxs will take care of that). What about if perl is - can we
really get away without not using LFS when perl is?
we can get away with it because Perl never passes lfs
, d_sigaction=define
usethreads=undef use5005threads=undef useithreads=undef usemultiplicity=undef
useperlio=undef d_sfio=undef uselargefiles=define
use64bitint=undef use64bitall=undef uselongdouble=undef usesocks=undef
Compiler:
cc='cc', optimize='-O', gccversion=2.95.2 19991024
On Fri, Dec 22, 2000 at 06:11:51PM -0800, Doug MacEachern wrote:
the 5.6.0+ uselargefile flags: -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
are still the source of many core dump reports. i just committed a patch
to rip them out by default. mod_perl does not need them. but they can be
On Fri, Dec 22, 2000 at 06:11:51PM -0800, Doug MacEachern wrote:
the 5.6.0+ uselargefile flags: -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
are still the source of many core dump reports. i just committed a patch
to rip them out by default. mod_perl does not need them. but they can be
the 5.6.0+ uselargefile flags: -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
are still the source of many core dump reports. i just committed a patch
to rip them out by default. mod_perl does not need them. but they can be
turned back on with Makefile.PL PERL_USELARGEFILES=1
i've tested with
On Fri, 22 Dec 2000, Doug MacEachern wrote:
the 5.6.0+ uselargefile flags: -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
are still the source of many core dump reports. i just committed a patch
to rip them out by default. mod_perl does not need them. but they can be
turned back on with
