Dear package maintainers:
The following line in debian/rules is commented out:
#AP2_CONFLAGS += -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
Please turn large file support (back) on!
Without it, the apr_off_t type used internally by Apache will be only
32-bits wide, thus causing the reported problem.
I realize that this will break the module ABI (and force a rebuild of
all already-packaged Apache2 modules). But releasing Sarge with
its flagwhip webserver sans large file support seems a bit silly.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-1-686-smp
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages libapr0 depends on:
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
ii libdb4.2 4.2.52-18 Berkeley v4.2 Database Libraries [
ii libexpat1 1.95.8-1 XML parsing C library - runtime li
ii libpcre3 4.5-1.1 Perl 5 Compatible Regular Expressi
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
We know.
> Without it, the apr_off_t type used internally by Apache will be only
> 32-bits wide, thus causing the reported problem.
We know.
> I realize that this will break the module ABI (and force a rebuild of
> all already-packaged Apache2 modules). But releasing Sarge with its
> flagwhip webserver sans large file support seems a bit silly.
This just isn't going to happen. We already did this dance once (turning
on LFS, then turning it back off when a few interesting bugs cropped up as
a result). We'll have LFS in Apache 2.1 and libapr1, not before.
... Adam