This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Surprising behavior of AM_CONDITIONAL

Hi,

Phil Edwards <phil@jaj.com> writes:

> On Thu, Jun 05, 2003 at 03:01:20PM -0500, Raja R Harinath wrote:
>> 
>> Newer versions of Automake include a check in the 'configure' script
>> that check at 'configure' time that all CONDITIONALs were evaluated.
>
> Do you know how recent a version?

Here's the ChangeLog entry from Automake:

  2001-12-30  Tom Tromey  <tromey@redhat.com>
  [snip]
        For PR automake/220:
        * tests/Makefile.am (TESTS): Added pr220.test.
        * tests/pr220.test: New file.
        * m4/cond.m4 (AM_CONDITIONAL): Cause creation of config.status to
        fail if conditional was never run.

I think it's in Automake 1.6 at least.  This feature depend so using
autoconf 2.52 or later, though -- so it's not immediately applicable.

In principle, even with this feature, your other suggestion of moving
all AM_CONDITIONALs to the toplevel seems better, even though you
lose some locality of reference.

- Hari
-- 
Raja R Harinath ------------------------------ harinath@cs.umn.edu
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]