statvfs() weirdness on alpha (RH-7.2 and CentOS-4.2)

Oliver Falk oliver at linux-kernel.at
Mon Nov 14 09:37:46 UTC 2005


On 11/14/2005 07:48 AM, Sergey Tikhonov wrote:
[ ... ]
>> Got it. The problem is in glibc with statvfs/statvfs64 functions on 
>> alpha (X86_64 doesn't have such problems).
>> As far as I understood statvfs64 is mapped to statvfs function on 64 
>> bit machines, but "struct statvfs" has 32 bits long
>> fields on alpha if compiled without any specific 64bits macros and the 
>> same fields become 64 bits long if compiled with
>> -D_LARGEILE64_SOURCE -D_FILE_OFFSET_BITS=64. The problem is that glibc 
>> is compiled with 32 bits long fields,
>> but packages like python,perl,gnome uses the macros defined above 
>> during building. I might be wrong in my findings, but after
>> recompilation python and gnome packages started to work.
>>
>> For now I changed 64-bits fields in /usr/inclide/bits/typesizes.h 
>> (__FSBLKCNT64_T_TYPE and __FSFILECNT64_T_TYPE) from
>> from __S64_TYPE/__U64_TYPE to __S32_TYPE/__S64_TYPE. Making evething 
>> 64-bits would require to rebuild whole AC2 tree. :(
> 
> Sorry: __S64_TYPE/__U64_TYPE to __S32_TYPE/__U32_TYPE

OK, this sounds like a fix, that should hit mainstream as well and maybe 
the RH/FC glibc packages (if they're willing to cooperate)... I hope 
you're going to post that to the gnu-people?

Best,
  Oliver




More information about the axp-list mailing list