On Tue, 2012-04-10 at 12:02 -0400, Paul Dugas wrote: > Yeah, that was your thread. I'm a little surprised, as you > were back > then, that this isn't something more people want to do. I was > trying > to accomplish the exact approach you were suggesting; using > the > installed package if it's there then falling back to a > sub-package if > it's not. I'll take a look at your macro. Thanks much. > > > Trying to use your macro today simply replacing my AC_CONFIG_SUBDIRS() > call with AX_CONFIG_DIR(). Seems that my script to bootstrap the > build system is no longer recursing into the sub-package. Looked at > the repository where you have the macro and don't see where it's > used. Wonder if you could point me in the right direction. http://code.google.com/p/audacity/source/browse/audacity-src/trunk/m4/audacity_checklib_widgetextra.m4 It won't help with your auto-bootstrap I suspect, because I expect that is scanning for certain hard-coded macro names to detect recursion, and it won't know about my macro (because it re-implements rather than wrapping, there is nothing to catch the recursion). This is likely to cause problems with some of the other "auto" features as well - I expect it to break the --help=recursive option to configure, but that's broken already for Audacity, so I didn't test. Richard _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx https://lists.gnu.org/mailman/listinfo/autoconf
