Eric Blake wrote:
> The problem is not a native compile, but a cross-compile ... I guess my
> original complaint should have made that more explicit.
Indeed. It was hard to guess so, while you were talking about failed tests
and 'fpclassify' results :-)
> configure:15398: checking whether isnanl
Bruno Haible clisp.org> writes:
>
> Eric Blake wrote:
> > gnulib's test-isnanl currently dies on mingw
>
> I don't observe this. Just did a
>
>./gnulib-tool --create-megatestdir --dir=/dev/shm/testdir1 --with-tests \
> isnan-nolibm isnanl-nolibm isnanl vasnprintf-posix
>
Eric Blake wrote:
> gnulib's test-isnanl currently dies on mingw
I don't observe this. Just did a
./gnulib-tool --create-megatestdir --dir=/dev/shm/testdir1 --with-tests \
isnan-nolibm isnanl-nolibm isnanl vasnprintf-posix
configured it on mingw (msys), and all tests pass. No
gnulib's test-isnanl currently dies on mingw, so we need to update the
configure test to account for the brokenness of the native isnanl.
fpclassify on mingw is documented to return only these five values:
#define FP_NAN 0x0100
#define FP_NORMAL 0x0400
#define FP_INFINITE (FP_N
