Re: automake/220: if foo rules evaluating true when no else clause present

[Tom Tromey <tromey at redhat dot com>]

The following reply was made to PR automake/220; it has been noted by GNATS.

From: Tom Tromey <tromey@redhat.com>
To: Richard Boulton <richard@tartarus.org>
Cc: robert.collins@itdomain.com.au, automake-gnats@sourceware.cygnus.com
Subject: Re: automake/220: if foo rules evaluating true when no else clause present
Date: 14 Aug 2001 16:34:08 -0600

 >>>>> "Richard" == Richard Boulton <richard@tartarus.org> writes:
 
 Richard> Perhaps the fix is to add a paragraph to the documentation
 Richard> saying that you must ensure that AM_CONDITIONAL is placed
 Richard> where it will always be executed, and citing
 
 I agree.  I've added this to my to-do list.
 
 Richard> Perhaps we could also add a configure-time check so that the code
 Richard> 	if test "x$NEVER_TRUE_TRUE" = "x$NEVER_TRUE_FALSE"; then
 Richard> 	  <emit a warning that the AM_CONDITIONAL has been used incorrectly
 Richard> 	  for NEVER_TRUE>
 Richard> 	fi
 Richard> gets added at the place where config.status is being built
 Richard> up.  I don't know autoconf well enough to do this.
 
 Offhand I don't know if this is possible.  It might be.
 
 Tom