>From: Eli Zaretskii
>Sent: Friday, December 28, 2012 7:13 PM
>To: MinGW Users List
>Subject: Re: [Mingw-users] strtod has changed from 4.5.2 to 4.7.0
>> Date: Fri, 28 Dec 2012 11:22:09 +0400
>> From: LRN
>> > What are the options I have for getting the behaviour that I prefer
>> > ?
>> If mingwrt was compiled without INFNAN_CHECK, and if it's mingwrt that
>> provides strtod for you (it's difficult for me to tell, but most
>> likely it is), then there's nothing you can do, short of re-building
>I think there _are_ other options. One is to have strtod in the
>sources compiled for the program, and make sure the INFNAN_CHECK is
>set there. Another is to have a small private library with the
>"fixed" strtod, and mention that library on the link command line
>before any system libraries. Finally, one could downgrade (or
>upgrade?) to another version of mingwrt, where this problem doesn't
Thanks guys for the quick response.
I'm using a gcc-4.7.0 binary that I downloaded from mingw.org a month or two
back - as mingw-get-inst-20120426.exe, I think.
The 'gcc -v' for it is provided below my sig.
Is there a suitable mingwrt that I can download and install over the top of
the existing installation ?
That would be my preferred option.
How would I tell beforehand whether that binary has been built with
INFNAN_CHECK ? ... or would I just have to try it out and see ?
Using built-in specs.
../gcc-4.7.0/configure --enable-languages=c,c++,ada,fortran,objc,obj-c++ --disable-sjlj-exceptions
--with-dwarf2 --enable-shared --enable-libgomp --disable-win32-registry --enable-libstdcxx-debug
Thread model: win32
gcc version 4.7.0 (GCC)