[opa-nightly-tests] Fwd: honest3 OPA_Daily_Tests_0817Tue_FAILED!!!

[Dave Goodell]

On Aug 19, 2010, at 2:44 PM CDT, Larry Knox wrote:

> I still got the message about adding AC_PROG_LIBTOOL to configure.in, but
> consulting Mike learned that I needed to run "libtoolize" before "autoreconf
> -vif".

This might indicate that your automake and libtool packages are installed in different directories.  "autoreconf -vif" is supposed to take care of running libtoolize for you.  But due to arcane and extremely boring reasons, autoreconf doesn't do this correctly when libtool and automake live separately.  You are supposed to be able to pass "-I /path/to/aclocal/macro/dir" to autoreconf as well, but it doesn't work reliably across various versions of the autotools.

> This works and the tests pass.  However, the following files are generated
> by running "libtoolize":
> 
> ?       confdb/ltsugar.m4
> ?       confdb/libtool.m4
> ?       confdb/ltversion.m4
> ?       confdb/lt~obsolete.m4
> ?       confdb/config.guess
> ?       confdb/ltoptions.m4
> ?       confdb/config.sub
> ?       confdb/ltmain.sh
> 
> These all seem to be necessary for the updated configure.  Do we check them
> in, or does someone know a way around to avoid that?

No, don't check them in.  These would be distributed with a source tarball, but shouldn't live in source control (at least, under our current autotools usage model).  The nightly testing script should be running "autoreconf -vif" nightly instead to incorporate any new configure/automake updates.  However, the autoreconf can happen on any machine single machine, unlike configure, provided that the source tree is then synched up on all the various testing platforms.

-Dave