Ok -
This comes from the Makefile.PL:
sub uselargefiles_check {
return unless $] >= 5.006 and $Config{uselargefiles}
and $PERL_USELARGEFILES and $USE_APXS;
local $Apache::src::APXS = $WITH_APXS;
my $cflags = Apache::src->new->apxs('-q' => 'CFLAGS') || '';
return if $cflags =~ /LARGEFILE/;
$PERL_USELARGEFILES=0; #just do it since
return; #nobody seems to listen to the warning below
phat_warn(<<EOF);
Your Perl is uselargefiles enabled, but Apache is not, suggestions:
*) Rebuild mod_perl with Makefile.PL PERL_USELARGEFILES=0
*) Rebuild Apache with CFLAGS="-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64"
*) Rebuild Perl with Configure -Uuselargefiles
*) Let mod_perl build Apache (USE_DSO=1 instead of USE_APXS=1)
EOF
}
As you can see it suggests rebuilding mod_perl with $PERL_USELARGEFILES=0 (which we
do) so according to him it will work?
If not then I'll mail Doug and tell him to add a conditional statement :)
Jaco Greyling
-----Original Message-----
From: Ged Haywood [mailto:[EMAIL PROTECTED]
Sent: 18 June 2003 13:06
To: Greyling, Jaco
Cc: mod_perl Mailing List
Subject: RE: non-LFS Apache 1.3.27 w/ LFS Perl 5.8.0 (using mod_perl)
Hi there,
On Wed, 18 Jun 2003 [EMAIL PROTECTED] wrote:
> Thus without re-compiling my whole Perl 5.8.0 build I need to come
> up with a solution.
I really don't see why you don't recompile your Perl. It's not a big
deal and it's going to be a lot safer that way.
> Sorry for my ignorance but it does look like it will work (non-LFS
> Apache) provided that you don't try to access files larger then 2GB.
I can't tell you how much what you're proposing to do worries me.
I wouldn't dream of doing it on one of my servers, not even on a
development machine.
The size of the files you access isn't the issue. It's the size of
the variables in the C data structures. If different parts of the
same code disagree about that, and they pass each other pointers to
different shaped structures, you are going to have serious problems.
As Stas said, the *best* you can hope for is an immediate crash of
some sort. It's possibile however that the problems might not surface
immediately and that the symptoms might not be obvious. You could
have all kinds of data corruption before you know what's hit you.
73,
Ged.
Visit our website at http://www.ubs.com
This message contains confidential information and is intended only
for the individual named. If you are not the named addressee you
should not disseminate, distribute or copy this e-mail. Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses. The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission. If
verification is required please request a hard-copy version. This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.
