Compiling with __USE_LARGEFILE64 on linux (RH8).

[Scott Greig <sg...@altair.com>]

I'm building an application that requires large file support enabled
(__USE_LARGEFILE64).  I'm finding apr_dir_read does not populate
apr_finfo_t correctly and as a result the fname field contains garbage.
If I remove the __USE_LARGEFILE64 flag it work correctly.

I thought I'd check if anyone else has had this problem before I look
for a solution.

Thanks
- Scott

Re: Compiling with __USE_LARGEFILE64 on linux (RH8).

[Garrett Rooney <ro...@electricjellyfish.net>]

On 5/12/06, Scott Greig <sg...@altair.com> wrote:
>
> I'm building an application that requires large file support enabled
> (__USE_LARGEFILE64).  I'm finding apr_dir_read does not populate
> apr_finfo_t correctly and as a result the fname field contains garbage.
> If I remove the __USE_LARGEFILE64 flag it work correctly.
>
> I thought I'd check if anyone else has had this problem before I look
> for a solution.

If I understand correctly, you can't just define __USE_LARGEFILE64 and
expect APR to work with large files.  Depending on the version of APR
you're using you can compile it with LFS support, and then it will
work, but that's not quite the same thing.

-garrett