[Gluster-infra] Updating automake for preparing release tar ball

[Anoop C S]

Hi all,

Few weeks before a community user reported to gluster-users ML[1] that
he/she encountered the following error while trying to do make install
from glusterfs sources(v3.7.11):

> Making install in glupy
>  /usr/bin/mkdir -p '/usr/lib/python2.7/site-packages/gluster/glupy'
>  /usr/bin/install -c -m 644 __init__.py '/usr/lib/python2.7/site-
> packages/gluster/glupy'
> ../../../../../py-compile: Missing argument to --destdir.
> make[6]: *** [install-pyglupyPYTHON] Error 1
> make[5]: *** [install-am] Error 2
> make[4]: *** [install-recursive] Error 1
> make[3]: *** [install-recursive] Error 1
> make[2]: *** [install-recursive] Error 1
> make[1]: *** [install-recursive] Error 1
> make: *** [install-recursive] Error 1

2 days back another user reported the same issue on gluster-dev irc
channel. I have provided the workaround temporarily.

>From my analysis this happens due to the use of old automake
version(v1.11.1) while preparing the release tar ball. Starting from
v1.11.2[2] automake has begun to accept empty arguments to --destdir
option for auto generated py-compile script for byte compiling python
code. Even if user have installed a version of automake >= 1.11.2
he/she will be presented with the above mentioned error during make
install as we have py-compile script included in the tar ball using
automake v1.11.1.

Can we have automake updated to some version >=1.11.2?

[1] http://www.gluster.org/pipermail/gluster-devel/2016-May/049501.html

[2] http://git.savannah.gnu.org/cgit/automake.git/tree/NEWS?id=v1.11.2
	see 4th bullet point under "Miscellaneous changes" section


Thanks,
-Anoop C S.