Over the weekend, I installed MirBSD. Out of the box, it includes only
automake-1.4 and a wrapper script 'automake' that has some pretty nasty
behavior:
$ automake --version
Provide an AUTOMAKE_VERSION environment variable, please
$ echo $?
0
$ AUTOMAKE_VERSION=1.4 automake --version | head -n1
automake (GNU automake) 1.4-p6
The Mir Ports project also includes automake 1.9.6, but that's the
extent of pre-compiled builds provided by the distro. (Obviously, they
aren't aware of the security bugs in only providing such old versions).
At any rate, this causes spurious test suite failures in 2.67:
35: tools.at:1162 autom4te preselections
243: torture.at:1399 Configuring subdirectories
248: torture.at:1780 Unusual Automake inupt files
All because the --version succeeded but didn't include a valid version
number. I'll have to figure out a way to skip these tests in the face
of MirBSD's broken automake wrapper script.
By the way, MirBSD's stock autoconf is equally broken in the same manner
(and the valid pre-installed choices there are 2.13 and 2.61, and lack
of AUTOCONF_VERSION in the environment gives 0 exit status without a
valid version string).
--
Eric Blake ebl...@redhat.com +1-801-349-2682
Libvirt virtualization library http://libvirt.org
