Re: [bug-gnu-libiconv] Sporadical Issues with GNU libiconv when using C++

[Bruno Haible]

Hi,

Pedro F. Giffuni wrote:
> When building OpenOffice on FreeBSD I occasionally see some very
> nasty error messages:
> ______
> ...
> Making:    all_jvmfwk.dpslo
> Compiling: jvmfwk/unxfbsdx.pro/misc/jvmfwk_version.c
> Compiling: jvmfwk/source/framework.cxx
> In file included from /usr/local/include/libxml2/libxml/encoding.h:28,
>                  from /usr/local/include/libxml2/libxml/parser.h:807,
>                  from
> /usr/ports/editors/openoffice.org-3-devel/work/ooo/main/jvmfwk/source/elements.hxx:35,
>                  from
> /usr/ports/editors/openoffice.org-3-devel/work/ooo/main/jvmfwk/source/framework.cxx:43:
> /usr/local/include/iconv.h:114: error: 'mbstate_t' does not name a type
> dmake:  Error code 1, while making '../unxfbsdx.pro/slo/framework.obj'
> ...
> 
> This is libiconv 1.13.1

Possibly this is fixed in libiconv 1.14, through this commit:

http://git.savannah.gnu.org/gitweb/?p=libiconv.git;a=commitdiff;h=a47098b3779b9febf25e8a5ba1b0407e29d67acf

> Curiously this error comes and goes every month, probably
> depending on the phase of the moon ;-).

There is very little software that depends on the phase of the moon.
Other than calendars and astronomy, here is an example:
http://bzr.savannah.gnu.org/lh/hello/trunk/annotate/head:/tests/greeting-2

Bruno