On 07/21/11 02:16, Herb Wartens wrote: > > > I have added a hack to get coreutils to compile cleanly on OSX. > > Thanks, but we should fix this problem more cleanly. Does the > following patch to lib/stdint.in.h solve your problem? This fix is > already scheduled to appear in the next version of coreutils. If it > doesn't solve your problem, what are the symptoms of failure? > > I agree. Fixing it more cleanly would definitely be better! The patch I sent was a hack just to get coreutils compiling cleanly. The patch you sent does indeed remove the compiler warnings I was seeing when printing integers with the PRIuMAX and PRIdMAX macros on OSX. I am still seeing the fdatasync warnings though.
- bug#9140: Coreutils Bug on OSX 10.7 (Lion) Herb Wartens
- bug#9141: Coreutils Compiler Warnings on OSX 10.7 (... Herb Wartens
- bug#9141: Coreutils Compiler Warnings on OSX 10... Paul Eggert
- bug#9141: Coreutils Compiler Warnings on OS... Herb Wartens
- bug#9141: Coreutils Compiler Warnings o... Paul Eggert
- bug#9141: Coreutils Compiler Warnings on OSX 10... Paul Eggert
- bug#9141: Coreutils Compiler Warnings on OS... Herb Wartens
- bug#9141: [PATCH 1/3] extensions: Enable extens... Paul Eggert
- bug#9141: [PATCH 1/3] extensions: Enable ex... Bruno Haible
- bug#9141: [PATCH 1/3] extensions: Enabl... Paul Eggert
- bug#9141: [PATCH 1/3] extensions: Enable ex... Voelker, Bernhard
- bug#9141: [PATCH 1/3] extensions: Enabl... Paul Eggert
- bug#9141: [PATCH 1/3] extensions: ... Voelker, Bernhard
- bug#9141: fdatasync module proposal Paul Eggert
