Script started on Fri 30 Dec 2016 06:22:42 AM EST sh-4.2$ cd /tmp sh-4.2$ tar xJf ~/Downloads/automake-1.15.tar.xz sh-4.2$ cd automake-1.15/ sh-4.2$ ./configure --prefix=/tmp/address@hidden checking whether make supports nested variables... yes checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /usr/bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether ln -s works... yes checking for perl... /usr/local/bin/perl checking for tex... tex checking for yacc... yacc checking for lex... lex checking whether autoconf is installed... yes checking whether autoconf works... yes checking whether autoconf is recent enough... yes checking whether ln works... yes checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for fgrep... /usr/bin/grep -F configure: will now look for a sturdy POSIX shell, for our testsuite checking for sh... /usr/bin/sh checking for sh5... no checking for dash... /usr/bin/dash checking for ash... no checking for bash... /usr/local/bin/bash checking for zsh... /usr/local/bin/zsh checking for ksh... /usr/bin/ksh checking for pdksh... no checking whether /usr/bin/sh supports $(cmd)... yes checking whether /usr/bin/sh supports $((expr))... yes checking whether /usr/bin/sh supports ${#var}... yes checking whether /usr/bin/sh supports ${var#glob} and ${var%glob}... yes checking whether /usr/bin/sh preserves exit traps with "set -e"... yes checking whether /usr/bin/sh can define exit traps in a shell function... yes checking whether /usr/bin/sh corrupts stderr with "set -x"... no checking whether /usr/bin/sh can return early from "dot-sourced" files... yes checking whether /usr/bin/sh supports alias named like shell builtins... yes checking whether /usr/bin/sh supports "test -e"... yes configure: shell /usr/bin/sh is good enough, stop looking configure: will use /usr/bin/sh as the testsuite shell configure: will now look for generic compilers checking for cc... cc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether cc accepts -g... yes checking for cc option to accept ISO C89... none needed checking whether cc understands -c and -o together... yes checking for aCC... no checking for CC... no checking for FCC... no checking for KCC... no checking for RCC... no checking for xlC_r... no checking for xlC... no checking for c++... c++ checking whether the C++ compiler works... yes checking for C++ compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C++ compiler... yes checking whether c++ accepts -g... yes checking for xlf95... no checking for f95... f95 checking whether the Fortran compiler works... yes checking for Fortran compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU Fortran compiler... yes checking whether f95 accepts -g... yes checking for xlf... no checking for f77... no checking for frt... no checking for pgf77... no checking for cf77... no checking for fort77... no checking for fl32... no checking for af77... no checking for g77... no checking for gfortran... gfortran checking whether the Fortran 77 compiler works... yes checking for Fortran 77 compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU Fortran 77 compiler... yes checking whether gfortran accepts -g... yes configure: will now look for GNU compilers configure: cc is already a GNU C compiler configure: c++ is already a GNU C++ compiler configure: f95 is already a GNU Fortran compiler configure: gfortran is already a GNU Fortran 77 compiler checking for gcj... no checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: creating t/wrap/aclocal-1.15 config.status: creating t/wrap/automake-1.15 sh-4.2$ make GEN bin/automake GEN bin/aclocal GEN t/ax/shell-no-trail-bslash GEN t/ax/cc-no-c-o GEN runtest GEN doc/aclocal.1 GEN doc/automake.1 GEN lib/Automake/Config.pm GEN doc/aclocal-1.15.1 help2man: can't get `--help' info from aclocal-1.15 Try `--no-discard-stderr' if option outputs to stderr make: *** [doc/aclocal-1.15.1] Error 2 sh-4.2$ t/wrap/aclocal-1.15 --help Possible unintended interpolation of @ke in string at /tmp/automake-1.15/bin/aclocal line 72. Global symbol "@ke" requires explicit package name at /tmp/automake-1.15/bin/aclocal line 72. BEGIN not safe after errors--compilation aborted at /tmp/automake-1.15/bin/aclocal line 119. Compilation failed in require at t/wrap/aclocal-1.15 line 29. sh-4.2$ exit exit Script done on Fri 30 Dec 2016 06:23:41 AM EST