On 4/12/2012 21:47, Christer Solskogen wrote:
> On 12/4/2012 12:56 PM, JonY wrote:
>> On 4/12/2012 18:14, Christer Solskogen wrote:
>>> On 2/4/2012 3:21 PM, Earnie Boyd wrote:
On Mon, Apr 2, 2012 at 6:28 AM, Christer Solskogen wrote:
> diff -r 57225b741f27 mingw-w64/mingw-w64-headers/confi
On Thu, Apr 12, 2012 at 11:10 AM, niXman wrote:
> 2012/4/12 Earnie Boyd :
>> On Thu, Apr 12, 2012 at 7:04 AM, niXman wrote:
>>> I.e. these warnings is reported when building gcc.
>>>
>>> ../../../mingw-src/gcc-trunk/gcc/lto-streamer.c:173:5: warning: ISO C
>>> does not support the 'I64' ms_printf
2012/4/12 Earnie Boyd :
> On Thu, Apr 12, 2012 at 7:04 AM, niXman wrote:
>> I.e. these warnings is reported when building gcc.
>>
>> ../../../mingw-src/gcc-trunk/gcc/lto-streamer.c:173:5: warning: ISO C
>> does not support the 'I64' ms_printf length modifier [-Wformat]
>
> Add -Wno-format after the
On 12/4/2012 12:56 PM, JonY wrote:
> On 4/12/2012 18:14, Christer Solskogen wrote:
>> On 2/4/2012 3:21 PM, Earnie Boyd wrote:
>>> On Mon, Apr 2, 2012 at 6:28 AM, Christer Solskogen wrote:
diff -r 57225b741f27 mingw-w64/mingw-w64-headers/configure
--- a/mingw-w64/mingw-w64-headers/configur
2012/4/12 Jonathan Liu
> Hi,
>
> I am getting some inconsistencies for the C pow() function between
> MinGW-w64 and Visual C++:
>
> compare(INFINITY, pow(-INFINITY, 3.1));
> Compared values are not the same (test.cpp:145)
> Expected (INFINITY): 1.#INF00
> Actual (pow(-INFINITY, 3.1)): -1.#IND
On Thu, Apr 12, 2012 at 7:04 AM, niXman wrote:
> I.e. these warnings is reported when building gcc.
>
> ../../../mingw-src/gcc-trunk/gcc/lto-streamer.c:173:5: warning: ISO C
> does not support the 'I64' ms_printf length modifier [-Wformat]
Add -Wno-format after the -pedantic.
--
Earnie
-- https:
Hi all,
John, Thank you so much for your guidance. As suggested, i added the "-F
pe-i386" flag in the windres command of makefile generated for minimal. So,
could run and see the output. I may need to use any of the "expat,
tiff,jpeg, zlib, regex,png" packages in my project. So, pl can anyone
su
Hi,
I am getting some inconsistencies for the C pow() function between
MinGW-w64 and Visual C++:
compare(INFINITY, pow(-INFINITY, 3.1));
Compared values are not the same (test.cpp:145)
Expected (INFINITY): 1.#INF00
Actual (pow(-INFINITY, 3.1)): -1.#IND00
compare(+INFINITY, 1.0/pow(-INFI
It seems that some code may be built using "-pedantic" ... which can
imply `__STRICT_ANSI__'.
On Thu, Apr 12, 2012 at 7:04 PM, niXman wrote:
> I.e. these warnings is reported when building gcc.
>
> example:
> x86_64-w64-mingw32-gcc -c -O2 -pipe -fomit-frame-pointer
> -momit-leaf-frame-pointer -
I.e. these warnings is reported when building gcc.
example:
x86_64-w64-mingw32-gcc -c -O2 -pipe -fomit-frame-pointer
-momit-leaf-frame-pointer -I/./mingw-libs-x64/include
-D__USE_MINGW_ACCESS -DIN_GCC -W -Wall -Wwrite-strings -Wcast-qual
-Wstrict-prototypes -Wmissing-prototypes -Wmissing-forma
On 4/12/2012 18:14, Christer Solskogen wrote:
> On 2/4/2012 3:21 PM, Earnie Boyd wrote:
>> On Mon, Apr 2, 2012 at 6:28 AM, Christer Solskogen wrote:
>>> diff -r 57225b741f27 mingw-w64/mingw-w64-headers/configure
>>> --- a/mingw-w64/mingw-w64-headers/configure Mon Apr 02 08:55:41 2012
>>> +0200
On 2/4/2012 3:21 PM, Earnie Boyd wrote:
> On Mon, Apr 2, 2012 at 6:28 AM, Christer Solskogen wrote:
>> diff -r 57225b741f27 mingw-w64/mingw-w64-headers/configure
>> --- a/mingw-w64/mingw-w64-headers/configure Mon Apr 02 08:55:41 2012
>> +0200
>> +++ b/mingw-w64/mingw-w64-headers/configure M
12 matches
Mail list logo
