It appears to be possible that
gl_cvs_header_working_stdint_h may not be set when
the inttypes.m4 generated tests are run. It is
probably a good idea to just quote the variable
arguments to test in this case to ensure that the
'=' operator is used in a binary operator context.
Thanks,
-- Mark
2006-09-18 Mark D. Baushke <[EMAIL PROTECTED]>
* inttypes.m4 (gl_cv_header_working_stdint_h): Avoid
'test: =: unary operator expected' on Solaris 9.
(gl_cv_header_inttypes_h): Be consistent in quoting.
Index: inttypes.m4
===================================================================
RCS file: /sources/gnulib/gnulib/m4/inttypes.m4,v
retrieving revision 1.13
diff -u -p -u -p -r1.13 inttypes.m4
--- inttypes.m4 28 Aug 2006 20:56:50 -0000 1.13
+++ inttypes.m4 18 Sep 2006 08:05:41 -0000
@@ -23,8 +23,8 @@ AC_DEFUN([gl_INTTYPES_H],
dnl - that imaxabs, imaxdiv, strtoimax, strtoumax are declared,
dnl - some additional tests.
gl_cv_header_working_inttypes_h=no
- if test $gl_cv_header_working_stdint_h = yes \
- && test $gl_cv_header_inttypes_h = yes \
+ if test "$gl_cv_header_working_stdint_h" = yes \
+ && test "$gl_cv_header_inttypes_h" = yes \
&& test "$ac_cv_have_decl_imaxabs" = yes \
&& test "$ac_cv_have_decl_imaxdiv" = yes \
&& test "$ac_cv_have_decl_strtoimax" = yes \
