On my development machine, I am no longer able to regenerate the configure script, etc. with autoreconf -fi. From a clean clone of the git repository, autoreconf -fi produces the following:
[mjumper@dev-mjumper incubator-guacamole-server]$ autoreconf -fi
libtoolize: putting auxiliary files in '../..'.
libtoolize: copying file '../../ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:26: installing './compile'
configure.ac:26: installing './config.guess'
configure.ac:26: installing './config.sub'
configure.ac:22: installing './install-sh'
configure.ac:26: error: required file './ltmain.sh' not found
configure.ac:22: installing './missing'
src/common-ssh/Makefile.am: installing './depcomp'
parallel-tests: installing './test-driver'
autoreconf: automake failed with exit status: 1
The key weirdness here is "putting auxiliary files in '../..'", which in my case is autoreconf shoving "ltmain.sh" in my home directory, of all places. I'm not sure when this changed. It's not a regression, as the same issue occurs with a clean clone of 0.9.10-incubating.