-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Luca Lesinigo on 6/19/2008 1:38 AM: | Using m4-1.4.11, | | test-strtod.c:667: assertion failed | | Confirmed on an HPPA 2.0 with: | - gentoo's gcc-4.1.2 and glibc-2.7-r2 | - gentoo's gcc-4.2.4 and glibc-2.7-r2 | but all checks are successful on HPPA 2.0 with: | - gentoo's gcc-4.3.1 and glibc-2.8_p20080602
Thanks for the report. This has previously been reported; it is a combination of two bugs: older glibc's strtod(3) is not C99 compliant, and m4's configure file was only detecting a subset, rather than all, known glibc strtod bugs. Both problems have been fixed in the respective version control repositories. You can work around it by using 'gl_cv_func_strtod_works=no ./configure' instead of plain './configure'. Or you can try a snapshot of what will become the future m4 1.6: 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 | | I tried also on an x86_64 box with gcc-3.4.6 and glibc-2.6.1 and all | checks are successful. Because even older glibc has even more strtod(3) bugs, including one in the subset that m4 1.4.11's configure was detecting. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEUEARECAAYFAkhaV3YACgkQ84KuGfSFAYDTyACeITosIoX/8847k1sdt2yny+lk CUkAmPWdMMEbhbd8mTv/htU7wjwWNgM= =A8/t -----END PGP SIGNATURE-----
