Building as of 1.0.18 fails due to missing aclocal

[Matthew Horsfall]

Previously, a Perl module that I maintain (Memcached::libmemcached) that wraps libmemcached was able to build on Travis-CI:

  https://travis-ci.org/timbunce/Memcached-libmemcached/jobs/20770244

It would complain about missing aclocal files, but continue on anyway:

  cd src/libmemcached && make install
  CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/bash /home/travis/build/timbunce/Memcached-libmemcached/src/libmemcached/build-aux/missing --run aclocal-1.12 -I m4 -I libtest/m4
  /home/travis/build/timbunce/Memcached-libmemcached/src/libmemcached/build-aux/missing: line 51: aclocal-1.12: command not found
  WARNING: 'aclocal-1.12' is missing on your system. You should only need it if
  you modified 'acinclude.m4' or 'configure.ac'. You might want
  to install the Automake and Perl packages. Grab them from
  any GNU archive site.

With 1.0.18 though, it fails:

  https://travis-ci.org/timbunce/Memcached-libmemcached/jobs/22484346

With this output:

  cd src/libmemcached && make install
  CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/bash /home/travis/build/timbunce/Memcached-libmemcached/src/libmemcached/build-aux/missing aclocal-1.13 -I m4 -I libtest/m4
  /home/travis/build/timbunce/Memcached-libmemcached/src/libmemcached/build-aux/missing: line 81: aclocal-1.13: command not found
  WARNING: 'aclocal-1.13' is missing on your system.
  You should only need it if you modified 'acinclude.m4' or
  'configure.ac' or m4 files included by 'configure.ac'.
  The 'aclocal' program is part of the GNU Automake package:
  <http://www.gnu.org/software/automake>
  It also requires GNU Autoconf, GNU m4 and Perl in order to run:
  <http://www.gnu.org/software/autoconf>
  <http://www.gnu.org/software/m4/>
  <http://www.perl.org/>
  make: *** [aclocal.m4] Error 127
  Unable to build libmemcached: Error running cd src/libmemcached && make install

It looks like libmemcached/build-aux/missing would previously throw the above warning, attempt to behave like aclocal, and then exit 0.

Now, it seems to exit 127, and cause the build to fail.

For the most part, this succeeds building on my local computer (though I saw it fail once like above but I haven't been able to repeat it since.)

Why did this behaviour change? Is this a bug?

Thanks,

-- Matthew Horsfall (alh)

[Matthew Horsfall (wolfsage)]

Hello,

Any word on this?

Thanks,

-- Matthew Horsfall (alh)