This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFC] Make _FILE_OFFSET_BITS=64 default.


On Wed, Mar 19, 2014 at 01:53:11AM -0400, Mike Frysinger wrote:
> On Fri 14 Mar 2014 14:18:37 Rich Felker wrote:
> > On Thu, Mar 13, 2014 at 11:41:48PM -0700, Paul Eggert wrote:
> > > glibc's own fts.h refuses to compile if __USE_FILE_OFFSET64 is defined.
> > 
> > Known issue:
> > https://sourceware.org/bugzilla/show_bug.cgi?id=15838
> > 
> > As stated there, my preference would be deprecation this whole API.
> > Applications which need it can get a _working_ (unlike the glibc copy)
> > version of this functionality from third-party sources. Gnulib and BSD
> > both have working versions that don't have the 32-bit limitation.
> 
> so wouldn't the right answer be to import the latest gnulib version ?

No, because the ABI is incompatible with glibc's interface. The reason
glibc is stuck with the broken one and gnulib isn't is that glibc has
to maintain an ABI while gnulib doesn't.

Of course this could be fixed by adding a new fts64 interface in
glibc; the question is just whether it's better to do this or
deprecate the interface in libc (as it really has no need to be in
libc).

> is there a preference for fts over ftw ?  i've never actually used either 
> myself.

I've never used fts but it looks better than ftw..

Rich


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]