Eric Blake wrote:
> Cygwin 1.7 added wcwidth, and it does pass the test-wcwidth.c unit test. So
> we
> may want to consider modifying this patch to also exempt cygwin from the
> expensive tests.
This would make sense if the multibyte / wide char support in Cygwin was final.
But as you say, the
Bruno Haible clisp.org> writes:
> Your suggestion would lead to a correct autoconf test as well. But we try
> to make configure tests fast - run as few programs as possible, skip
> unnecessary tests. There's no big point in making the MacOS X test work
> in a 100% robust way on Cygwin and Solaris
Hello,
kc wrote:
> However, I was cross-compiling gettext-0.17 on x86_64-pc-linux-gnu for
> i686-pc-linux-gnu. gettext did not compile because it did not use the
> system wchar.h, but some other variant provided with the gettext's source
> tarball. The cause was that gettext's configure was
Dear Bruno,
On Mon, 13 Jul 2009 23:46:29 +0200, Bruno Haible wrote:
the attached patch solves two problems with the current version of
m4/wcwidth.m4 (serial 14). However, those two problems are so closely
related that I chose to attack them in one patch.
On which platform did you encounter a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Cygwin 1.7 now provides fpurge, and it passes test-fpurge.c without the
use of a wrapper function. Therefore, I think that it avoids the BSD bug
reported here:
http://lists.gnu.org/archive/html/bug-gnulib/2007-04/msg00277.html
That means that blindly
