Re: [PATCH] ash: support platforms that don't have '%m' printf specifier

2017-07-28 Thread Denys Vlasenko
On Thu, Jul 27, 2017 at 6:58 PM, Jody Bruchon wrote: > On 2017-07-27 12:16, Xabier Oneca -- xOneca wrote: >> >> Hello: >> >> 2017-07-27 17:48 GMT+02:00 Ron Yorston : >>> >>> Kang-Che Sung wrote: dietlibc supports %m only if WANT_ERROR_PRINTF is defined in when building, and its com

Re: [PATCH] ash: support platforms that don't have '%m' printf specifier

2017-07-28 Thread Denys Vlasenko
On Thu, Jul 27, 2017 at 2:53 PM, Ron Yorston wrote: > The '%m' conversion specifier prints an error message based on the > current value of 'errno'. It is available in the GNU C library, > Cygwin (since 2012), uClibc and musl. > > It is not available in various BSDs, BSD-derived systems (MacOS, >

Re: [PATCH] ash: support platforms that don't have '%m' printf specifier

2017-07-27 Thread Kang-Che Sung
On Fri, Jul 28, 2017 at 12:58 AM, Jody Bruchon wrote: > IMO the whole issue is that %m is non-standard despite having moderate de > facto acceptance in many libc implementations. I think BusyBox should comply > with the standards instead of having a compile-time hack and added code > complication

Re: [PATCH] ash: support platforms that don't have '%m' printf specifier

2017-07-27 Thread Jody Bruchon
On 2017-07-27 12:16, Xabier Oneca -- xOneca wrote: Hello: 2017-07-27 17:48 GMT+02:00 Ron Yorston : Kang-Che Sung wrote: dietlibc supports %m only if WANT_ERROR_PRINTF is defined in when building, and its commented out by default. I don't know how to check the macro WANT_ERROR_PRINTF in the di

Re: [PATCH] ash: support platforms that don't have '%m' printf specifier

2017-07-27 Thread Xabier Oneca -- xOneca
Hello: 2017-07-27 17:48 GMT+02:00 Ron Yorston : > Kang-Che Sung wrote: >>dietlibc supports %m only if WANT_ERROR_PRINTF is defined in >> when building, and its commented out by default. >>I don't know how to check the macro WANT_ERROR_PRINTF in >>the dietlibc build environment, but I think busybox

Re: [PATCH] ash: support platforms that don't have '%m' printf specifier

2017-07-27 Thread Ron Yorston
Kang-Che Sung wrote: >dietlibc supports %m only if WANT_ERROR_PRINTF is defined in > when building, and its commented out by default. >I don't know how to check the macro WANT_ERROR_PRINTF in >the dietlibc build environment, but I think busybox needs to be >aware of this. There doesn't seem to be

Re: [PATCH] ash: support platforms that don't have '%m' printf specifier

2017-07-27 Thread Kang-Che Sung
On Thu, Jul 27, 2017 at 8:53 PM, Ron Yorston wrote: > The '%m' conversion specifier prints an error message based on the > current value of 'errno'. It is available in the GNU C library, > Cygwin (since 2012), uClibc and musl. > > It is not available in various BSDs, BSD-derived systems (MacOS, >

[PATCH] ash: support platforms that don't have '%m' printf specifier

2017-07-27 Thread Ron Yorston
The '%m' conversion specifier prints an error message based on the current value of 'errno'. It is available in the GNU C library, Cygwin (since 2012), uClibc and musl. It is not available in various BSDs, BSD-derived systems (MacOS, Android) or Microsoft Windows. Use a symbol defined in platfor