Re: tracking a recursive macro

[Patrick Welche]

On Wed, Jul 06, 2005 at 09:41:41PM +0200, Ralf Wildenhues wrote:
> Are you aware of the recent macro loop in CVS HEAD/branch-2-0 Libtool in
> conjunction with special Autoconf versions?

/me checks it isn't 1 April...

nope

> Which exact Autoconf/Automake/Libtool versions do you use (if CVS
> versions include `head ChangeLog`).

autoconf of 5 July, automake and libtool of 4th.

autoconf:

2005-07-05  Stepan Kasal  <address@hidden>

        * lib/autoconf/status.m4 (_AC_CONFIG_DEPENDENCIES): Fix the
        description, the macro now accepts only a single tag.
        (_AC_CONFIG_UNIQUE): Likewise; s/AC_File/[$1]/

automake:

2005-07-02  Alexandre Duret-Lutz  <address@hidden>

        * doc/automake.texi (Public macros) <AM_WITH_DMALLOC>: Reword to
        fix an underful hbox.
        * lib/INSTALL, lib/config.guess, lib/config.sub, lib/texinfo.tex:
        New upstream version.

libtool:

2005-07-03  Thorsten Glaser  <address@hidden>

        * m4/libtool.m4 (_LT_TRY_DLOPEN_SELF): Quieten configure
        output for corner cases on some BSDs.
        (LT_CMD_MAX_LEN): Another comment cleanup.

        * config/ltmain.m4sh (func_extract_archives, func_mode_install),
        m4/libtool.m4 (_LT_SETUP, _LT_SYS_DYNAMIC_LINKER, LT_PATH_LD)
        (_LT_PATH_LD_GNU, _LT_LINKER_SHLIBS, _LT_LANG_CXX_CONFIG):
        Comment language, indentation, and backquote cleanup.
        * THANKS: Updated.

> > Now, that is the AC_OUTPUT line, and the last thing to appear in
> > autom4te.cache/traces.0t is
> > 
> > m4trace:configure.in:2084: -1- AC_SUBST([LIB@&address@hidden, [$ac_libobjs])
> > m4trace:configure.in:2084: -1- AC_SUBST_TRACE([LIB@&address@hidden)
> > m4trace:configure.in:2084: -1- m4_pattern_allow([^LIB@&address@hidden)
> > m4trace:configure.in:2084: -1- AC_SUBST([LTLIBOBJS], [$ac_ltlibobjs])
> > m4trace:configure.in:2084: -1- AC_SUBST_TRACE([LTLIBOBJS])
> > m4trace:configure.in:2084: -1- m4_pattern_allow([^LTLIBOBJS$])
> > 

> > Any idea how I can start to track this down?
> 
> Well, what I did was go back patches until I had the one, then go up and
> down macro calls and comment out random stuff to find out what's going
> on.

Divide and conquer.. Here goes - a mere 2084 of configure.in..

> Then I reported that I was stuck and Ralf Menzel came up with a
> fix (actually he tracked it down too, mostly).  :)
> 
> No, seriously, post something reproducible.  Someone will know..

Cheers,

Patrick