On Wed, Jul 30, 2008 at 2:22 AM, Eric Blake <[EMAIL PROTECTED]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > According to Dennis Clarke on 7/29/2008 7:48 PM: > | not too sure what the issue is here. > > | test-strtod.c:738: assertion failed > ... > | FAIL: test-strtod > > The issue is well-known.
Thank you for the quick reply. I did a little bit of research and have seen many other posts about this. I should do some research before I file a bug report next time. > Your libc is buggy when it comes to C99 > strtod(3) compliance, I am surprised to see that in Solaris 10. The Sun folks tend to be fascists about compliance to specs and standards and that is why I love them. see : http://www.blastwave.org/man/s10/standards_5.html where I see : Compilation A POSIX.1 (1988-1996)-, XPG4-, SUS-, or SUSv2-conforming implementation must include an ANSI X3.159-1989 (ANSI C Language) standard-conforming compilation system and the cc and c89 utilities. A POSIX.1-2001- or SUSv3-conforming implementation must include an ISO/IEC 99899:1999 (1999 ISO C Language) standard-conforming compilation system and the c99 utility. Solaris 10 was tested with the cc, c89, and c99 utilities and the compilation environment provided by Sun Studio C Compiler 5.6. At the very bottom of that page I also see : Similar SUSv3-conforming LP64 applications should be built with command lines of the form: c99 $(getconf POSIX_V6_LP64_OFF64_CFLAGS) -D_XOPEN_SOURCE=600 \ $(getconf POSIX_V6_LP64_OFF64_LDFLAGS) foo.c -o foo \ $(getconf POSIX_V6_LP64_OFF64_LIBS) -lxnet SUSv3 c99 _XOPEN_SOURCE=600 OKay ... so I'll go back and rebuild m4 1.4.11 with this : bash-3.2$ uname -a SunOS mercury 5.10 Generic_127128-11 i86pc i386 i86pc bash-3.2$ c99 -V cc: Sun C 5.9 SunOS_i386 Patch 124868-01 2007/07/12 usage: c99 [ options] files. Use 'c99 -flags' for details Also, I am going to have a hard look at the Sunsolve bug reports and patches released and see if there is anything filed about this. If there is a real concern about C99 compliance in libc then the Sun folks will know about it. > but the configure check in m4 1.4.11 didn't check > for all the known bugs in various libc's. You can use './configure > gl_cv_func_strtod_works=no' to work around it; or use the latest snapshot: > > http://home.comcast.net/~ericblake/m4-1.5.89a.31-d9538d.tar.gz > http://home.comcast.net/~ericblake/m4-1.5.89a.31-d9538d.tar.gz.asc > http://home.comcast.net/~ericblake/m4-1.5.89a.31-d9538d.tar.bz2 > http://home.comcast.net/~ericblake/m4-1.5.89a.31-d9538d.tar.bz2.asc > http://home.comcast.net/~ericblake/m4-1.5.89a.31-d9538d.tar.lzma > http://home.comcast.net/~ericblake/m4-1.5.89a.31-d9538d.tar.lzma.asc Oh well, thank you very much. I'll drag down one of those promptly and then see what happens after a build with c99 and after libc is patched. Oh, and I'll circle around and give you my progress report of that is okay. Dennis Clarke http://www.blastwave.org
