<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/3.26.0"> </HEAD> <BODY> On Mon, 2010-11-29 at 06:02 -0800, Dan Nicholson wrote: <BLOCKQUOTE TYPE=CITE> <TT>Pretty sure it's coming from libtoolize :)</TT> </BLOCKQUOTE> It does. <BLOCKQUOTE TYPE=CITE> <TT>libtoolize: Consider adding "AC_CONFIG_MACRO_DIR([m4])" to configure.ac and</TT> <TT>libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.</TT> <TT>libtoolize: Consider adding "-I m4" to ACLOCAL_AMFLAGS in Makefile.am.</TT> <TT>It's suggesting that you add AC_CONFIG_MACRO_DIR([m4]) so that it will</TT> <TT>helpfully install it's m4 files there and attempt to make them</TT> <TT>persistent. Jeremy Huddleston asked not to do this a while back</TT> <TT>because it's then harder to replace the included libtool with the</TT> <TT>patched version on OSX. Not sure if this is still a problem, but there</TT> <TT>are definitely pros and cons to distributing the libtool macros in the</TT> <TT>tree.</TT> </BLOCKQUOTE> There are quite a few modules having an m4 directory. This is where modules put their additional m4 macros (unrelated to libtool). There may be additional behaviours associated with having an m4 directory. It's still not clear to me. In any case, the libtool macros are shipped in aclocal.m4. I think the issue was libtool v2 versus 1.5. I don't think it's a problem anymore. The -I m4 should not be added when you have no macros in git. Libtool does not need that to work and it will break the build on a fresh repo clone because m4 cannot be found. </BODY> </HTML>