Re: Tests that fail due to iconv()

[Bruno Haible]

Avis, Ed wrote:
> I meant the configure script can print a message 'your iconv library
> is broken, please install GNU libiconv' and then exit. Or there could
> be an --allow-broken-iconv configure option, for users who are sure
> that their use of gettext won't be affected by their local iconv().

These are good suggestions, and I'd be tempted to implement them when
most systems come with a good iconv by default (in a year or two).

But configure scripts should also work in cross-compilation environments,
and I cannot distinguish a "good" from a "broken" iconv() in a cross-
compilation environment.

But my main argument is that the programs are still reliable in a
sense that even without an iconv(), they never produce wrong results
(they give an error message instead), and for some very limited use of
the tools the iconv() is not needed.

Bruno