Re: GNU gettext 0.18.3.1 fails with undefined _Bool on Solaris

[Paul Eggert]

I wouldn't worry about the ACL checks, as gettext doesn't rely on ACLs.

The _Bool thing is due to a problem in gettext's configure.ac files.
gettext-tools/configure.ac invokes gtpo_EARLY, which invokes
AM_PROG_CC_C_O, which means gettext-tools is configured with
'-D_STDC_C99=', so stdbool.h works; whereas gettext-runtime/configure.ac
does not do that, so gettext-runtime is not configured with '-D_STDC_C99=',
so stdbool.h does not work for it and it supplies a substitute, which
is incompatible with the system stdbool.h used by gettext-tools.

To work around the problem, configure gettext 0.18.3.1 this way:

./configure CC='cc -D_STDC_C99='

I did that, and got a successful build.  The build has a lot of warnings,
most of which look like minor bugs in gettext (notably mismatched types),
so I'll attach the log for the benefit of the gettext maintainer.

Here's an untested patch for GNU gettext which I hope fixes the _Bool problem.
Basically the idea is to use AM_PROG_CC_C_O consistently everywhere.
A similar patch may need to be applied in other directories that
do not use gtpo_EARLY.

--- gettext-runtime/configure.ac.old    2013-07-29 04:35:59.000000000 -0700
+++ gettext-runtime/configure.ac        2013-11-11 00:08:24.405322400 -0800
@@ -61,6 +61,7 @@

 dnl Make sure we see all GNU and Solaris extensions.
 gl_EARLY
+AM_PROG_CC_C_O

 dnl Check for build configuration.

log.gz
Description: application/gzip