_FILE_OFFSET_BITS 64 not supported (was: Re: WARNING fileutils 4.0x-1 severly broken
On Fri, Jul 28, 2000 at 06:53:28PM +0200, Marcus Brinkmann wrote:
> Do NOT install fileutils 4.0x-1 that's in the archive since
> It is utterly broken. Even the simplest functions like rm, ln
> return "Function not implemented"
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?
I have to use --disable-largefile on the Hurd, it seems.
Funnily, the autoconf check doesn't bother to check if largefiles are really
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?
`Rhubarb is no Egyptian god.' Debian http://www.debian.org Check Key server
Marcus Brinkmann GNU http://www.gnu.org for public PGP Key
Marcus.Brinkmann@ruhr-uni-bochum.de, email@example.com PGP Key ID 36E7CD09