apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Greig" <sgr...@altair.com>
Subject RE: Compiling with __USE_LARGEFILE64 on linux (RH8).
Date Fri, 12 May 2006 20:47:33 GMT
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

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

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

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

> -----Original Message-----
> From: rooneg@gmail.com [mailto:rooneg@gmail.com] On Behalf Of 
> 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).
> On 5/12/06, Scott Greig <sgreig@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

View raw message