Surprising behavior of AM_CONDITIONAL

[Raja R Harinath]

Hi,

Phil Edwards <phil@jaj.com> writes:

> A snippet of irc conversation:
>
>   [13:44:09] <pme> Here's the question:  we have some AM_CONDITIONAL
>      statements in configure, and in a Makefile.am, we have some
>      corresponding "if" statements.  What happens if the AM_CONDITIONAL
>      is never executed?
>   [13:44:49] <DannyB> pme: Nuclear holocaust?
>   [13:44:47] <pme> It /looks/ like neither the true nor false case gets a
>      '#' setting in config.status, which means that /both/ statements in
>      the Makefile are executed.
>   [13:45:21] <pme> I say "looks"... that's the behavior I'm actually seeing,
>      and my working theory is that the AM_CONDITIONAL isn't being run.
>   [13:46:49] <pme> ...and it really surprises me that  a binary conditional
>      defaults to "both".  :-(

Newer versions of Automake include a check in the 'configure' script
that check at 'configure' time that all CONDITIONALs were evaluated.
(So, yes, the way to figure out if the CONDITIONALs are not covered is
to hear from users tripping on the warning.)

- Hari
-- 
Raja R Harinath ------------------------------ harinath@cs.umn.edu