On Sat, Feb 2, 2013 at 4:24 PM, Roy Stogner <roystgnr@ices.utexas.edu> wrote:
And Ben's really gone above-and-beyond in making that easy.  The last
time I ran his bootstrap on a system where I'd forgotten to update
automake from an older version, the script detected that and then
built and used our contrib/autotools stuff instead.

I'm not sure how robust that is yet; if someone's found a system where
it doesn't work, I'd consider that a bug for us to fix.

One thing that didn't work but that might be too hard to fix: you
actually have to run bootstrap for it to work; e.g. if you merely do a
"make" after changing a .am file and automake gets automatically
re-run that way then (at least on Cygwin) it won't build the latest
automake for you first.

So you're saying it's not supposed to work like this:

~/src/libmesh$ ./bootstrap 
Using autoconf (autoreconf (GNU Autoconf) 2.69)
Using libtool (libtool (GNU libtool) 2.4.2)
Using automake (automake (GNU automake) 1.13.1)
...
~/src/libmesh$ git diff --shortstat
 80 files changed, 19707 insertions(+), 7912 deletions(-)