[Top][All Lists]

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

Re: Autoconf's `GUILE_CHECK' macro broken

From: Thien-Thi Nguyen
Subject: Re: Autoconf's `GUILE_CHECK' macro broken
Date: Tue, 13 Sep 2005 05:09:39 -0400

   From: address@hidden (Ludovic =?iso-8859-1?Q?Court=E8s?=)
   Date: Mon, 12 Sep 2005 17:27:12 +0200

   However, both versions of Guile return zero, regardless of whether
   the expression passed to `-c' returned false or not.

check out how the other macros in guile.m4 use GUILE_CHECK.  in each
case, the last form in the group of forms to be tested uses (exit ...).
the reason we leave it as a convention instead of codifying it into
GUILE_CHECK is to allow for multiple forms in the test (for example,

thanks for reporting this.  the next release of guile 1.4.x, will have
the appended documentation for GUILE_CHECK.  i suggest other branches
update accordingly.


# Usage: GUILE_CHECK(var,check)
# Set @var{var} to the numeric return value of evaluating @var{check}.
# @var{var} is a shell variable name to be set to the return value.
# @var{check} is one or more Guile Scheme expression, evaluated with
# "$GUILE -c", the last of which should return either 0 or non-#f to
# indicate the check passed.  Non-0 number or #f indicates failure.
# This is conventionally achieved by wrapping the last expression in
# @code{exit}.  For example, @code{(foo) (bar) (exit (baz))}.
# Avoid using the character "#" since that confuses autoconf.  

reply via email to

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