Adam Griffiths wrote:
In terms of mod_perl is it an error to have Perl compiled with LFS but not
Apache, or the other way around? In otherwords should LFS for the two
programs always mach? Or should mod_perl aplications be able to handle a
mismatch in LFS between Apache and Perl?
I guess I've faile
In terms of mod_perl is it an error to have Perl compiled with LFS but not
Apache, or the other way around? In otherwords should LFS for the two
programs always mach? Or should mod_perl aplications be able to handle a
mismatch in LFS between Apache and Perl?
"Stas Bekman" <[EMAIL PROTECTED]> wrote
Thanks Stas for your detailed reply.
I have apache 1.3. apxs -q cflags does not show any mention of
LARGEFILE_SOURCE neither does ap_config_auto.h, I guess that's definitive
answer...
Perl -V indicates USE_LARGE_FILES as a compile time option.
I'm not sure what mod_perl was compiled with but Ap
Adam Griffiths wrote:
Hi All,
How can I get a definitive answer as to whether mod_perl was compiled with
Large File Support?
I have a shell login account but not root.
It's complicated. Because Apache and Perl need to be compiled with LFS to
really "have" it under mod_perl. Many times you get Per
Hi All,
How can I get a definitive answer as to whether mod_perl was compiled with
Large File Support?
I have a shell login account but not root.
Regards
Adam
--
Reporting bugs: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
