Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (asf.osuosl.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Compiling with __USE_LARGEFILE64 on linux (RH8).
Date: Fri, 12 May 2006 16:47:33 -0400
Message-ID: <91FBE7AEE91B454282AE05FE79413A4A03678363@trexch.prog.altair.com>
Thread-Topic: Compiling with __USE_LARGEFILE64 on linux (RH8).
Thread-Index: AcZ16/A9SM5xgS0dRHquLQmIRsscnQAFo3GQ
From: "Scott Greig" <sgreig@altair.com>
To: "Garrett Rooney" <rooneg@electricjellyfish.net>
Cc: <dev@apr.apache.org>

I tried rebuilding apr(1.1.1) with LFS enabled.  There seemed to be a
problem with simply passing '--enable-lfs' to configure.  The configure
script temporarily adds the -D__USE_LARGEFILE64 then removes it using
$apr_save_CPPFLAGS?

So I forced it to add -D__USE_LARGEFILE64 to CPPFLAGS and setting
APR_HAS_LARGE_FILES=3D1.
Still the apr_dir_read fails to return the correct file names.=20

After further investigation I found that linux has a readdir64 function
that takes a dirent64 structure neither appear to be used by
apr/file_io/unix/dir.c?  I'm looking into adding support to
apr_arch_file_io.h

Let me know if I'm missing something.
Thanks
- Scott

> -----Original Message-----
> From: rooneg@gmail.com [mailto:rooneg@gmail.com] On Behalf Of=20
> Garrett Rooney
> Sent: Friday, May 12, 2006 1:46 PM
> To: Scott Greig
> Cc: dev@apr.apache.org
> Subject: Re: Compiling with __USE_LARGEFILE64 on linux (RH8).
>=20
> On 5/12/06, Scott Greig <sgreig@altair.com> wrote:
> >
> > I'm building an application that requires large file=20
> support enabled=20
> > (__USE_LARGEFILE64).  I'm finding apr_dir_read does not populate=20
> > apr_finfo_t correctly and as a result the fname field=20
> contains garbage.
> > If I remove the __USE_LARGEFILE64 flag it work correctly.
> >
> > I thought I'd check if anyone else has had this problem=20
> before I look=20
> > for a solution.
>=20
> If I understand correctly, you can't just define=20
> __USE_LARGEFILE64 and expect APR to work with large files. =20
> Depending on the version of APR you're using you can compile=20
> it with LFS support, and then it will work, but that's not=20
> quite the same thing.
>=20
> -garrett
>=20