Re: m4-1.4.11 strtod test failure

2008-04-03 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Bob Friesenhahn on 4/3/2008 8:14 PM: | If I sound a bit harsh on Linux's "enhanced" strtod() it is because it | cost me several days worth of time to work-around it. GraphicsMagick | uses many arguments of the form NxN (in thousands of p

Re: m4-1.4.11 strtod test failure

2008-04-03 Thread Bob Friesenhahn
On Thu, 3 Apr 2008, Eric Blake wrote: is not strict enough at filtering out bugs. Since all of your failures are with hex-floats, and gnulib's version handles those, I'm guessing that configure guessed (wrongly) that your strtod is working. Therefore, if you want to reconfigure with 'gl_cv_func

Re: m4-1.4.11 strtod test failure

2008-04-03 Thread Bob Friesenhahn
On Thu, 3 Apr 2008, Eric Blake wrote: According to Bob Friesenhahn on 4/3/2008 10:15 AM: | Under Solaris 10U4 x86, m4's strtod test blows up. Hopefully the code | does not now rely on Linux glibc's strtod irritatingly "wrong" behavior | related to supposed "hex" values. I see that the lines wh

Re: m4-1.4.11 strtod test failure

2008-04-03 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Bob Friesenhahn on 4/3/2008 10:15 AM: | Under Solaris 10U4 x86, m4's strtod test blows up. Hopefully the code | does not now rely on Linux glibc's strtod irritatingly "wrong" behavior | related to supposed "hex" values. I see that the l

m4-1.4.11 strtod test failure

2008-04-03 Thread Bob Friesenhahn
Under Solaris 10U4 x86, m4's strtod test blows up. Hopefully the code does not now rely on Linux glibc's strtod irritatingly "wrong" behavior related to supposed "hex" values. I see that the lines which fail include a comment which lists all of the known operating systems in the universe exce