[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-gettext] gettext-tools test failures on Darwin

From: Daiki Ueno
Subject: Re: [bug-gettext] gettext-tools test failures on Darwin
Date: Thu, 20 Dec 2012 18:15:04 +0900
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)

(Cc'ed Paul, regarding gettext test failures on Mac OS X)

Daiki Ueno <address@hidden> writes:

> I've just got access to a Darwin 12 machine and tried to build gettext
> git master on it.  Fortunately the build succeeded.  It seems that the
> stpncpy issue[1], which I was concerned about, was already fixed in
> gnulib.
> However, there are still 6 of 327 test failures:
> http://du-a.org/~ueno/gettext/gettext-tools-make-check-darwin.txt

FAIL: gettext-7
FAIL: msgmerge-compendium-6
FAIL: format-sh-1
FAIL: lang-c++
FAIL: lang-sh
FAIL: lang-bash

Sorry, lang-c++ and lang-sh were false-negatives (gettext-runtime was
not built correctly here).  Also, maybe msgmerge-compendium-6,
format-sh-1, and lang-bash can be ignored since it seems that the
failures are due to sed shipped in Mac OS X.

The only thing that needs to be fixed is gettext-7.  The error is
basically because of the gettext translit feature[1], which is triggered
when locale_charset() returns "ASCII".

After the following change (in gnulib), locale_charset() returns "ASCII"
on Mac OS X, even if thread's locale is set to "de_DE.UTF-8", say.  So
the solution would be either to make sure MB_CUR_MAX > 1 somehow in the
test, or to make locale_charset() thread-safe.

commit 0cd711b27ba11019c96314a42e197bc288f415d7
Author: Paul Eggert <address@hidden>
Date:   Sun Sep 16 10:47:43 2012 -0700

    localcharset: work around Mac OS X bug with UTF-8 and MB_CUR_MAX
    * lib/localcharset.c (locale_charset) [DARWIN7]:
    Return "ASCII" if the system reports "UTF-8" and MB_CUR_MAX <= 1,
    as these two values are incompatible.  Problem reported by Max Horn.
    For more discussion, please see


[1]  https://gnu.org/software/gettext/FAQ.html#translit

Daiki Ueno

reply via email to

[Prev in Thread] Current Thread [Next in Thread]