Re: Android port

[Po Lu]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Po Lu <luangruo@yahoo.com>
>> Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
>> Date: Fri, 04 Aug 2023 17:44:11 +0800
>> 
>> Thanks.  What about after applying the following change and rerunning
>> configure?
>> 
>> diff --git a/nt/mingw-cfg.site b/nt/mingw-cfg.site
>> index e8b4711f548..68e264fde4c 100644
>> --- a/nt/mingw-cfg.site
>> +++ b/nt/mingw-cfg.site
>> @@ -178,9 +178,11 @@ gl_cv_func_printf_sizes_c99=yes
>>  gl_cv_func_printf_long_double=yes
>>  gl_cv_func_printf_infinite_long_double=yes
>>  gl_cv_func_printf_directive_a=yes
>> +gl_cv_func_printf_directive_b=yes
>>  gl_cv_func_printf_directive_f=yes
>>  gl_cv_func_printf_directive_n=yes
>>  gl_cv_func_printf_directive_ls=yes
>> +gl_cv_func_printf_directive_lc=yes
>>  gl_cv_func_printf_positions=yes
>>  gl_cv_func_printf_flag_grouping=yes
>>  gl_cv_func_printf_flag_leftadjust=yes
>
> If MinGW doesn't support those directives, the above is not TRT, it
> might cause future maintenance headaches.
>
> I don't think MSVCRT.DLL's implementation of printf supports those, at
> least not on all versions of Windows.

Those flags are how Gnulib users are meant to disable the printf-posix
module, though.  Angelo, would you please provide your config.log?  It
would assist me in determining which printf features Gnulib is still
striving to replace.