RPI-4 arm64 with Ubuntu 20.04 LTS Server can't compile from source

[pr0logas]

ubuntu@rpi4:~/hstr-2.2$ cat /etc/issue
Ubuntu 20.04.1 LTS \n \l

ubuntu@rpi4:~/hstr-2.2$ cat /proc/cpuinfo | tail -n 1
Model       : Raspberry Pi 4 Model B Rev 1.2

Source code: https://github.com/dvorka/hstr/archive/2.2.tar.gz Installed deps:

sudo apt install automake gcc make libncursesw5-dev libreadline-dev pkg-config -y

ubuntu@rpi4:~/hstr-2.2$ ./configure 

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 make supports nested variables... yes
checking for gcc... gcc
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 gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking whether make supports the include directive... yes (GNU style)
checking dependency style of gcc... gcc3
checking build system type... aarch64-unknown-linux-gnu
checking host system type... aarch64-unknown-linux-gnu
checking for pkg-config... pkg-config
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for killwchar in -lncursesw... yes
checking for cos in -lm... yes
checking for using_history in -lreadline... yes
checking assert.h usability... yes
checking assert.h presence... yes
checking for assert.h... yes
checking ctype.h usability... yes
checking ctype.h presence... yes
checking for ctype.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking getopt.h usability... yes
checking getopt.h presence... yes
checking for getopt.h... yes
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking math.h usability... yes
checking math.h presence... yes
checking for math.h... yes
checking readline/history.h usability... yes
checking readline/history.h presence... yes
checking for readline/history.h... yes
checking regex.h usability... yes
checking regex.h presence... yes
checking for regex.h... yes
checking signal.h usability... yes
checking signal.h presence... yes
checking for signal.h... yes
checking stdbool.h usability... yes
checking stdbool.h presence... yes
checking for stdbool.h... yes
checking stddef.h usability... yes
checking stddef.h presence... yes
checking for stddef.h... yes
checking stdio.h usability... yes
checking stdio.h presence... yes
checking for stdio.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking sys/ioctl.h usability... yes
checking sys/ioctl.h presence... yes
checking for sys/ioctl.h... yes
checking termios.h usability... yes
checking termios.h presence... yes
checking for termios.h... yes
checking for unistd.h... (cached) yes
checking wchar.h usability... yes
checking wchar.h presence... yes
checking for wchar.h... yes
checking for stdbool.h that conforms to C99... (cached) yes
checking for _Bool... yes
checking for size_t... yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible malloc... yes
checking for memset... yes
checking for strdup... yes
checking for strstr... yes
checking for /tmp/hstr-ms-wsl... no
./configure: line 5036: syntax error near unexpected token `BASH_COMPLETION,'
./configure: line 5036: `    PKG_CHECK_MODULES(BASH_COMPLETION, bash-completion >= 2.0,'

[dvorka]

@pr0logas bash_completion is not required (it's just used for convenience) - perhaps you could comment it out in configure.ac. Simply comment/remove the whole section which installs bash completion (keep AC_OUTPUT).

[pr0logas]

Commented as you suggested like this:

[...]
# Bash CLI autocomplete
#AC_ARG_WITH([bash-completion-dir],
#    AS_HELP_STRING([--with-bash-completion-dir[=PATH]],
#        [Install the bash auto-completion script in this directory. @<:@default=yes@:>@]),
#    [],
#    [with_bash_completion_dir=yes])

#if test "x$with_bash_completion_dir" = "xyes"; then
    # pkg-config command existence for PKG_CHECK_MODULES macro checked above
#    PKG_CHECK_MODULES([BASH_COMPLETION], [bash-completion >= 2.0],
#        [BASH_COMPLETION_DIR="`pkg-config --variable=completionsdir bash-completion`"],
#        [BASH_COMPLETION_DIR="$datadir/bash-completion/completions"])
#else
#    BASH_COMPLETION_DIR="$with_bash_completion_dir"
#fi

#AC_SUBST([BASH_COMPLETION_DIR])
#AM_CONDITIONAL([ENABLE_BASH_COMPLETION],[test "x$with_bash_completion_dir" != "xno"])

AC_OUTPUT

moved a bit further but now getting another error:

ubuntu@rpi4:~/hstr-2.2$ ./configure 
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 make supports nested variables... yes
checking for gcc... gcc
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 gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking whether make supports the include directive... yes (GNU style)
checking dependency style of gcc... gcc3
checking build system type... aarch64-unknown-linux-gnu
checking host system type... aarch64-unknown-linux-gnu
checking for pkg-config... pkg-config
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for killwchar in -lncursesw... yes
checking for cos in -lm... yes
checking for using_history in -lreadline... yes
checking assert.h usability... yes
checking assert.h presence... yes
checking for assert.h... yes
checking ctype.h usability... yes
checking ctype.h presence... yes
checking for ctype.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking getopt.h usability... yes
checking getopt.h presence... yes
checking for getopt.h... yes
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking math.h usability... yes
checking math.h presence... yes
checking for math.h... yes
checking readline/history.h usability... yes
checking readline/history.h presence... yes
checking for readline/history.h... yes
checking regex.h usability... yes
checking regex.h presence... yes
checking for regex.h... yes
checking signal.h usability... yes
checking signal.h presence... yes
checking for signal.h... yes
checking stdbool.h usability... yes
checking stdbool.h presence... yes
checking for stdbool.h... yes
checking stddef.h usability... yes
checking stddef.h presence... yes
checking for stddef.h... yes
checking stdio.h usability... yes
checking stdio.h presence... yes
checking for stdio.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking sys/ioctl.h usability... yes
checking sys/ioctl.h presence... yes
checking for sys/ioctl.h... yes
checking termios.h usability... yes
checking termios.h presence... yes
checking for termios.h... yes
checking for unistd.h... (cached) yes
checking wchar.h usability... yes
checking wchar.h presence... yes
checking for wchar.h... yes
checking for stdbool.h that conforms to C99... (cached) yes
checking for _Bool... yes
checking for size_t... yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible malloc... yes
checking for memset... yes
checking for strdup... yes
checking for strstr... yes
checking for /tmp/hstr-ms-wsl... no
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: error: cannot find input file: `Makefile.in'

@dvorka

ubuntu@rpi4:~/hstr-2.2$ find . -name Makefile.in
ubuntu@rpi4:~/hstr-2.2$ find . -name Makefile*
./Makefile.am
./src/Makefile.am
./man/Makefile.am

[mikeymckay]

I had the same problem. I commented out all of the BASH_COMPLETION stuff and then set some variables:

# Bash CLI autocomplete

# Check whether --with-bash-completion-dir was given.
#if test "${with_bash_completion_dir+set}" = set; then :
#  withval=$with_bash_completion_dir;
#else
#  with_bash_completion_dir=yes
#fi

#if test "x$with_bash_completion_dir" = "xyes"; then
#    # pkg-config command existence for PKG_CHECK_MODULES macro checked above
#    PKG_CHECK_MODULES(BASH_COMPLETION, bash-completion >= 2.0,
#        BASH_COMPLETION_DIR="`pkg-config --variable=completionsdir bash-completion`",
#        BASH_COMPLETION_DIR="$datadir/bash-completion/completions")
#else
#    BASH_COMPLETION_DIR="$with_bash_completion_dir"
#fi

# if test "x$with_bash_completion_dir" != "xno"; then
#  ENABLE_BASH_COMPLETION_TRUE=
#  ENABLE_BASH_COMPLETION_FALSE='#'
#else
#  ENABLE_BASH_COMPLETION_TRUE='#'
#  ENABLE_BASH_COMPLETION_FALSE=
#fi
ENABLE_BASH_COMPLETION_TRUE='#'
ENABLE_BASH_COMPLETION_FALSE=