> The configuration scripts in those builds don't generate largefile-aware > mod_perl shared objects which seems to cause random cores in file access. > I suspect this to be the same bug earlier seen by Hyoung-Kee Choi [1]. > > My hack was to modify /opt/apache2/bin/apr-config to the largefile defines > to CPPFLAGS. > > Is it an Apache bug that apr-config does not include my CFLAGS and > CPPFLAGS?
we've played around with this before, and I thought that stas and joe had it licked, but maybe not. you can take a cruise through this (long) thread and see. starting here http://marc.theaimsgroup.com/?l=apache-modperl-dev&m=108079557016990&w=2 with a good explanation of the problem here http://marc.theaimsgroup.com/?l=apache-modperl-dev&m=108091576021446&w=2 the net result of the thread is that the mod_perl build system was fixed so that it magically made sure that perl and apache were in sync where required for largefile support. but perhaps the fix wasn't quite as thorough as required for your platform, compiler, or whatnot. I'd suggest distilling the issue and moving to dev@ where it's more likely to get attention from those that did the work before and grok this stuff (which isn't me :) --Geoff -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
