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
Paul Eggert wrote:
> So, instead of this:
>
> if (flags >= 16)
> type = TYPE_U32_STRING;
> else if (flags >= 8)
> type = TYPE_U16_STRING;
> else
> type = TYPE_U8_STRING;
>
> I might use something
Jim Meyering <[EMAIL PROTECTED]> writes:
>>type = TYPE_U8_STRING + (8 <= flags) + (16 <= flags);
> For that one-liner, you must be playing devil's advocate or something,
I suppose I was :-). Still, if performance is important and if we
like computing with 'int' the idea could be
Ralf Wildenhues <[EMAIL PROTECTED]> writes:
> To meet posix requirements, the sed script needs newlines after `{' and
> instead of all the `;', see autoconf manual.
Thanks for catching and reporting that. I installed this patch to gnulib:
2007-06-12 Paul Eggert <[EMAIL PROTECTED]>
*
Paul Eggert <[EMAIL PROTECTED]> wrote:
> Bruno Haible <[EMAIL PROTECTED]> writes:
>
>> Hey, 'int' is a flexible data type!
>
> I agree, though for this particular example I find the code
> easier to read if the test is ordered numerically, and if an
> if-then-else expression is used. So, instead
Bruno Haible <[EMAIL PROTECTED]> writes:
> Hey, 'int' is a flexible data type!
I agree, though for this particular example I find the code
easier to read if the test is ordered numerically, and if an
if-then-else expression is used. So, instead of this:
if (flags >= 16)
Jim Meyering <[EMAIL PROTECTED]> writes:
> That will ensure that you use the regex code bundled with coreutils,
> which may be less buggy than what's in your systems C library.
In the meantime it shouldn't hurt to test for the buggy regexp he
mentioned. I installed this into gnulib:
2007-06-12
