Re: header file mismatch for struct statfs and linux

[Andreas Schwab]

Chris Friesen <address@hidden> writes:

|> The glibc header file for struct statfs defines the following fields:
|> 
|>      __fsblkcnt_t f_blocks;
|>      __fsblkcnt_t f_bfree;
|>      __fsblkcnt_t f_bavail;
|> 
|> where __fsblkcnt_t is defined as:
|> 
|> typedef unsigned int __fsblkcnt_t;
|> 
|> This causes problems since the linux kernel (and "man statfs") defines
|> these entries as type long.

On architecture where int == long this does not make any difference.  On
ia64 at least the type is correctly defined.

|> As well, I believe POSIX says that they are supposed to be longs.

POSIX does not define statfs nor <sys/statfs.h>, and it requires
fsblkcnt_t to be an unsigned integer type, but nothing more.

Andreas.

-- 
Andreas Schwab, SuSE Labs, address@hidden
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."