Re: _FILE_OFFSET_BITS 64 not supported (was: Re: WARNING fileutils 4.0x-1 severly broken

[Roland McGrath <roland@gnu.org>]

> The culprit is that fileutils now defines _FILE_OFFSET_BITS 64 on the Hurd,
> which sucks in functions like readdir64, lseek64 etc
> 
> backupfile.o(.text+0x154): warning: readdir64 is not implemented and will always fail
> cp.o: In function `main':
> cp.o(.text+0x150d): warning: stat64 is not implemented and will always fail
> copy.o: In function `copy_reg':
> copy.o(.text+0x63e): warning: lseek64 is not implemented and will always fail
> 
> Can we easily implement those?

We could, but there should be autoconf checks for these that notice them as
stubs.  Is gnu-stubs.h right?

> I have to use --disable-largefile on the Hurd, it seems.
> 
> Funnily, the autoconf check doesn't bother to check if largefiles are really
> supported.
> 
> checking for special C compiler options needed for large files... no
> checking for _FILE_OFFSET_BITS value needed for large files... 64
> checking for _LARGEFILE_SOURCE value needed for large files... no
> checking for _LARGE_FILES value needed for large files... no
> checking for _XOPEN_SOURCE value needed for large files... no
> 
> Is this a bug in fileutils?

Oh, yes it surely is.  It should have checks for each *64 function.