Mosh requires aclocal to support the --install flag, which wasn't added until automake version 1.10*. Since all of the version checking (AC_PREREQ and such) is performed by aclocal itself, checking to see if install is supported must be done before aclocal itself is called. Ideally the restriction would be lifted in the future, but for now at least supply users with a less cryptic message than 'unrecognized option --install' *source: http://git.savannah.gnu.org/cgit/automake.git/tree/NEWS?id=v1.11.1&h=next&=switch Signed-off-by: Pat Pannuto <firstname.lastname@example.org>
…detect the system's poll is broken
Also increases maximum frame rate from 50 fps to 100 fps. Relevant to issue #222 on github.
Closes #225 github issue (Jay Freeman).
Otherwise that variable has no effect.
Suggested by Kees Cook.
Through Autoconf we set hardening flags that are actually more aggressive than the Ubuntu defaults, but they conflict with same.
The previous code had the following issues: 1) hardcoded the path of /bin/sh (should use paths.h) 2) threw away the variable with the fallback shell 3) prepended - to the path rather than the shell name 4) added a - before explicit chosen non-shell commands Closes #199.
There appears to be a typo/thinko in the ncurses detection stuff in configure.ac. The fallout was that on a Linux host without ncurses-devel installed, "./configure" failed to find curses.h but claimed overall success, then the build failed later during make. This patch removes an extraneous comma, which seems to make it both fail and succeed correctly when it should.