I actually can't convince myself that changing APR_HAS_LARGE_FILES to be 0 on APR HEAD when LFS support is *enabled* is the right thing to do; it just doesn't make sense.
I think the right way to solve this is to make mod_perl's has_large_files_conflict/strip_lfs functions a bit more smarter, I'll follow up with a more concrete proposal tomorrow.
I doubt this has anything to do with has_large_files_conflict. It's only used to decide whether we can allow seek() with non-zero offset. The segfaulting happens much much earlier.
(well, actually, the Right Place to solve this is to get Perl to not do anything really silly like export -D_FILE_OFFSET_BITS=64 in the first place, but hey)
Why do you find that silly? If perl was built with these options, other apps linking that library also need to build with this option. If not there will be a mismatch in what perl and the app think about the size of several data types.
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
