GNOME Bugzilla – Bug 520464
Bad AC_CONDITIONAL syntax
Last modified: 2012-02-28 13:28:11 UTC
In the "Checks for libgcrypt" section of configure.in of libgnomedb-3.1.2 (and also in SVN trunk), there is: AM_CONDITIONAL(HAVE_LIBGCRYPT, 0) The second field of that macro is evaluated by the shell, not passed as a simple number. As written, the configure script is generated as: if 0; then HAVE_LIBGCRYPT_TRUE= HAVE_LIBGCRYPT_FALSE='#' else HAVE_LIBGCRYPT_TRUE='#' HAVE_LIBGCRYPT_FALSE= fi which is a shell syntax error ("0: no such command"). If you want to force the token to be false, pass "false": AM_CONDITIONAL(HAVE_LIBGCRYPT, false)
"libgnomedb" will not see active development anymore according to its developers. It has been superseded by libgda. Closing this report as WONTFIX - Please feel free to reopen this bug report in the future if anyone takes the responsibility for active development again.