From: Keith M. <kei...@us...> - 2008-02-20 20:21:59
|
On Wednesday 20 February 2008 18:41, Earnie Boyd wrote: > >> creating t-sub.exe > >> make[4]: Leaving directory `/home/Rob/comp/gmp-4.2.2/tests' > >> make check-TESTS > >> make[4]: Entering directory `/home/Rob/comp/gmp-4.2.2/tests > >> FAIL: t-bswap.exe > >> FAIL: t-constants.exe > >> FAIL: t-count_zeros.exe > >> FAIL: t-gmpmax.exe > >> FAIL: t-hightomask.exe > >> FAIL: t-modlinv.exe > >> FAIL: t-popc.exe > >> FAIL: t-parity.exe > >> FAIL: t-sub.exe > > > > I'd say you need to enable verbosity on these tests and find out > > exactly the nature of the failure. > > I usually find that the problem with tests like these are static > files that contain unix line endings The `static' files in question being the reference data, provided with the package, for what the output of the tests should be. > and the comparison of the output > from the test contains microsoft line endings. \n is different from > \r\n so the test is marked as failed since the output is different. > Convert the static file to microsoft line endings and the test > suddenly passes. Yep. I've noticed this too. At one time, while attempting to build a native version of GNU m4, every one of its tests failed; I can't remember now, just how many tests were involved, but I think it was around 80. All but two of the failures were directly attributable to this `\n' vs. `\r\n' distinction. Regards, Keith. |