Hello Gary, * Gary V. Vaughan wrote on Sat, Oct 09, 2010 at 05:48:04AM CEST: > I had to autoreconf to get rid of a ton of spurious configure time errors > on my Mac... oddly, the first autoreconf threw up a ton of unset AC_LANG > warnings, but when I reran autorecong to log them for later investigation > - they disappeared. > > ...ah, that's because autoreconf is still running aclocal before libtoolize, > Wow!, I thought that had been fixed a long time ago. It kinda-sorta works > because the libtool macros are m4_included from the generated aclocal.m4, > and libtoolize overwrites the out-of-date libtool macro files before > autoconf picks them up. Oh well... aclocal is going away eventually anyway.
autoreconf runs aclocal to find out by tracing whether AC_PROG_LIBTOOL is used, then runs libtoolize if needed, then runs aclocal again if needed. I think that is just about the right way to do it, barring extra warnings. I haven't looked at your recently posted tracing script for whether that does this much differently, but I'm guessing not. Cheers, Ralf
