Hi,
Apache 2.2.x in SFW includes a patch (which basically adds
"-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64" to CFLAGS) to enable large file
support.
It looks like this patch was added at the time of Apache 2.0.x,
when APR 0.9 didn't do that automatically. But APR >= 1.x does
?-D_LARGEFILE64_SOURCE? by default.
Thanks to Jeff (cc'd) for pointing out that these flags were no longer
needed for Apache 2.2 builds.
But, if we remove them, we'd be incompatible with the modules written and
compiled using
a previous SFW Apache 2.2 build. So, users would have to rebuild their modules
using the
apache-without-old-largefile-flags build. On the other hand, this fix enables
the external
modules built using the typically-compiled apache to work with our build.
Please suggest if we can document this incompatibility and go ahead with the
change in
the upcoming build or should we wait till the next major release of APR, to fix
this ?
I tried the below scenarios to test the compatibility.
Note: typically-compiled apache means apache configured and built with default
options as below:
MAKE=/usr/ccs/bin/make CC=/opt/SUNWspro/bin/cc ./configure --prefix=/foo
--enable-so --enable-mods-shared=all
- typically-compiled apache and php built using typically-compiled apache :
typically-compiled apache worked fine.
- typically-compiled apache and php built using apache-of-b95 (which is also
2.2.8 but doesn't have this fix):
typically-compiled apache dumped core.
- typically-compiled apache and php built using apache-with-fix (with
-D_LARGEFILE64_SOURCE,
without -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64):
typically-compiled apache worked fine.
- apache-of-b95 and php built using typically-compiled apache:
apache-of-b95 dumped core.
- apache-of-b95 and php built using apache-with-fix:
apache-of-b95 dumped core.
- apache-with-fix and php built using typically-compiled apache:
apache-with-fix worked fine.
- apache-with-fix and php built using apache-of-b95:
apache-with-fix dumped core.
Thanks in advance,
Seema.
