On 9/12/2017 8:22 PM, Liu Hao wrote:
> On 2017/9/13 0:15, Eli Zaretskii wrote:
>>> You'd need to disassemble (or at least check with nm) the
>>> object/function to find out if it's calling __mingw_printf or regular
>>> printf, seems like emacs is using %lld and %I64 in different places.
>>
>> %lld
On 2017/9/13 0:15, Eli Zaretskii wrote:
You'd need to disassemble (or at least check with nm) the
object/function to find out if it's calling __mingw_printf or regular
printf, seems like emacs is using %lld and %I64 in different places.
%lld is used for intmax_t values, %I64d is used for
> Date: Mon, 11 Sep 2017 23:46:00 +
> From: JonY via Mingw-w64-public
> Cc: JonY
>
> > . GCC doesn't recognize the PRIdMAX format spec, defined in
> > MinGW64 inntypes.h header as "lld";
> > . GCC doesn't
> From:
> Date: Tue, 12 Sep 2017 10:05:12 +1000
>
> Not sure what to make of the format warnings (I'll leave that to others),
> but I think the post that you cited does reveal an instance of Emacs doing
> something wrong wrt the redefining of _WIN32_WINNT.
> This
-Original Message-
From: Eli Zaretskii
Sent: Tuesday, September 12, 2017 3:19 AM
To: mingw-w64-public@lists.sourceforge.net
Subject: [Mingw-w64-public] Problems with using printf format specs with GCC
7
Does Emacs do anything wrong in these cases?
Not sure what to make
On 09/11/2017 05:19 PM, Eli Zaretskii wrote:
> Hi,
>
> Kindly take a look at the issues with building current development
> sources of GNU Emacs with MinGW64, described here:
>
> http://lists.gnu.org/archive/html/emacs-devel/2017-09/msg00171.html
>
> The build emits a lot of warnings related