Patch attached.
--
Best regards,
ltpmouse
From 35656690a3eb69ac5694de27081e9213df2eec79 Mon Sep 17 00:00:00 2001
From: Liu Hao
Date: Tue, 27 Jun 2017 23:57:39 +0800
Subject: [PATCH] mingw-w64-headers/crt/_mingw_print_pop.h: Do not check for
_INC_STDIO or _WSTDIO_DEFINED
On 25.06.2017 20:39, Liu Hao wrote:
I've checked and both _POSIX_C_SOURCE=1 and __USE_MINGW_ANSI_STDIO=1
don't affect this define.
>>> It should, at least the latter one should show effect. Of course you
>>> need to define it before including inttypes.h
>> Very simple test case:
>>
Hello Kai,
Friday, June 23, 2017, 5:55:39 PM, you wrote:
>> I've checked and both _POSIX_C_SOURCE=1 and __USE_MINGW_ANSI_STDIO=1
>> don't affect this define.
> It should, at least the latter one should show effect. Of course you
> need to define it before including inttypes.h
Very simple test
2017-06-22 18:41 GMT+02:00 Lev Serebryakov :
> On 22.06.2017 16:17, Kai Tietz via Mingw-w64-public wrote:
>
>> Be welcome. Well, actually gcc has one paragraph about this. You can
>> find it in gcc's extend.texi. It is part of the item 'format
>> (@var{archetype}, ...'
On 22.06.2017 16:17, Kai Tietz via Mingw-w64-public wrote:
> Be welcome. Well, actually gcc has one paragraph about this. You can
> find it in gcc's extend.texi. It is part of the item 'format
> (@var{archetype}, ...' about attributes.
I've looked at GCC online documentation :) It mention
2017-06-22 14:19 GMT+02:00 Lev Serebryakov :
> On 22.06.2017 15:12, Kai Tietz via Mingw-w64-public wrote:
>
>> Well, your issue is "(format (printf, ... )". First use __printf, or
>> even better __printf__. Nevertheless the printf formatter is
>> representing the default
On 22.06.2017 15:12, Kai Tietz via Mingw-w64-public wrote:
> Well, your issue is "(format (printf, ... )". First use __printf, or
> even better __printf__. Nevertheless the printf formatter is
> representing the default print-formatter style. That is obviously on
> Windows not the gnu-ish
2017-06-22 13:39 GMT+02:00 Lev Serebryakov :
> Hello Liu,
>
> Thursday, June 22, 2017, 4:46:33 AM, you wrote:
>
So, I need to printf() uint64_t in my project, which is built in strict
ISO C11 mode and with all warnings enabled.
>>>
If I try to use "%llu"
Hello Liu,
Thursday, June 22, 2017, 4:46:33 AM, you wrote:
>>> So, I need to printf() uint64_t in my project, which is built in strict
>>> ISO C11 mode and with all warnings enabled.
>>
>>> If I try to use "%llu" I get warning that "unknown conversion type
>>> character 'l' in format". If I
2017-06-22 4:53 GMT+02:00 :
> -Original Message- From: Liu Hao
> Sent: Thursday, June 22, 2017 11:46 AM
> To: mingw-w64-public@lists.sourceforge.net
> Subject: Re: [Mingw-w64-public] how to printf() 64-bit integer in 64-bit
> compiler in strict ISO mode with all
-Original Message-
From: Liu Hao
Sent: Thursday, June 22, 2017 11:46 AM
To: mingw-w64-public@lists.sourceforge.net
Subject: Re: [Mingw-w64-public] how to printf() 64-bit integer in 64-bit
compiler in strict ISO mode with all warnings enabled?
So, I need to printf() uint64_t in my
On 2017/6/22 6:30, Lev Serebryakov wrote:
Hello Lev,
Wednesday, June 21, 2017, 11:41:45 PM, you wrote:
So, I need to printf() uint64_t in my project, which is built in strict
ISO C11 mode and with all warnings enabled.
If I try to use "%llu" I get warning that "unknown conversion type
Hello Lev,
Wednesday, June 21, 2017, 11:41:45 PM, you wrote:
> So, I need to printf() uint64_t in my project, which is built in strict
> ISO C11 mode and with all warnings enabled.
> If I try to use "%llu" I get warning that "unknown conversion type
> character 'l' in format". If I use
Here are problem, which was discussed in the past, but without this
"all warnings enabled" part.
So, I need to printf() uint64_t in my project, which is built in strict
ISO C11 mode and with all warnings enabled.
If I try to use "%llu" I get warning that "unknown conversion type
character
14 matches
Mail list logo