bug#7572: ping

2011-07-23 Thread Jim Meyering
Ludwig Nussel wrote: > Are there any concerns with the patch? It would be really nice to > have this merged upstream to avoid further fragmentation. If you now have a complete patch (including documentation, NEWS update and a good ChangeLog), please post it. Or, if you opted not to pursue this, p

bug#9140: Coreutils Bug on OSX 10.7 (Lion)

2011-07-23 Thread Bruno Haible
Paul Eggert wrote: > Subject: [PATCH 3/3] fsusage: port to MacOS X 10.7 with 4 TiB file systems > > * m4/fsusage.m4 (gl_FILE_SYSTEM_USAGE): Reject statvfs > implementations that use only 32 bits to count blocks. But this change has also effects on other platforms than MacOS X 10.7: - On glibc/Hu

bug#9140: fsusage: add large volume support on glibc/Hurd, HP-UX 11, Solaris, MacOS X

2011-07-23 Thread Bruno Haible
> 1) To require AC_SYS_LARGEFILE, and a module dependency to 'largefile'. >This will make statvfs() use a 64-bit f_blocks on >glibc/Hurd, MacOS X >= 10.4, HP-UX, Solaris. Here's the first proposed patch. I verified that - on HP-UX 11.00 and 11.31, Solaris 7 and 10, it causes statvfs() to

bug#9140: fsusage: revert unintended change on AIX, Cygwin, Interix

2011-07-23 Thread Bruno Haible
> 2) To undo the patch that introduces check_f_blocks_size, because > - on MacOS X 10.7 it is not needed any more after 1), > - on AIX and Cywin it causes non-POSIX API to be used for no reason, > - it kills portability to Interix 3.5. Slight correction: It is still needed after 1),

bug#9140: Coreutils Bug on OSX 10.7 (Lion)

2011-07-23 Thread Jim Meyering
Bruno Haible wrote: > Paul Eggert wrote: >> Subject: [PATCH 3/3] fsusage: port to MacOS X 10.7 with 4 TiB file systems >> >> * m4/fsusage.m4 (gl_FILE_SYSTEM_USAGE): Reject statvfs >> implementations that use only 32 bits to count blocks. > > But this change has also effects on other platforms than

bug#9140: fsusage: add large volume support on glibc/Hurd, HP-UX 11, Solaris, MacOS X

2011-07-23 Thread Jim Meyering
Bruno Haible wrote: >> 1) To require AC_SYS_LARGEFILE, and a module dependency to 'largefile'. >>This will make statvfs() use a 64-bit f_blocks on >>glibc/Hurd, MacOS X >= 10.4, HP-UX, Solaris. > > Here's the first proposed patch. I verified that > > - on HP-UX 11.00 and 11.31, Solaris 7 an

bug#9140: fsusage: revert unintended change on AIX, Cygwin, Interix

2011-07-23 Thread Jim Meyering
Bruno Haible wrote: >> 2) To undo the patch that introduces check_f_blocks_size, because >> - on MacOS X 10.7 it is not needed any more after 1), >> - on AIX and Cywin it causes non-POSIX API to be used for no reason, >> - it kills portability to Interix 3.5. > > Slight correction: I

bug#9140: fsusage: add large volume support on AIX

2011-07-23 Thread Bruno Haible
> 3) To make use of statvfs64 on AIX. Here's the proposed patch for it. As expected we get: - On AIX 5.2, 6.1, 7.1: checking whether to use statvfs64... yes - On AIX 5.1, HP-UX, IRIX, Solaris: checking whether to use statvfs64... no 2011-07-23 Bruno Haible fsusage: Enable

bug#9140: fsusage: add large volume support on AIX

2011-07-23 Thread Paul Eggert
Thanks for all that work in analysis, and porting checking, for statvfs etc. Your patches look good to me too.

bug#9141: [PATCH 1/3] extensions: Enable extensions on MacOS X 10.5 and later.

2011-07-23 Thread Paul Eggert
On 07/22/11 17:23, Bruno Haible wrote: > The usual idiom in the MacOS X header files is > > #if !defined(_POSIX_C_SOURCE) || defined(_DARWIN_C_SOURCE) > > So, I expect that your change will be a no-op for almost everyone. Thanks for the clarification. I looked through what I could glean from