Hello, When building http://ftp.gnu.org/gnu/autoconf/autoconf-2.69.tar.xz using Bash 5.0, make check reports many failures concerning the following Bash 5.0's change of behavior, quoting https://lists.gnu.org/archive/html/bug-bash/2019-01/msg00063.html:
There are a few incompatible changes between bash-4.4 and bash-5.0. [...] By default, the shell only sets BASH_ARGC and BASH_ARGV at startup if extended debugging mode is enabled; it was an oversight that it was set unconditionally and caused performance issues when scripts were passed large numbers of arguments. End quote. A sample test failure is as follows: +--- at_config_vars-state-env.r1 2020-02-20 15:01:43.684855852 +0000 ++++ at_config_vars-state-env.r2 2020-02-20 15:01:43.688855866 +0000 +@@ -2,8 +2,8 @@ + BASH=/bin/sh + BASHOPTS=checkwinsize:cmdhist:complete_fullquote:extquote:force_fignore:globasciiranges:hostcomplete:interactive_comments:progcomp:promptvars:sourcepath + BASH_ALIASES=() +-BASH_ARGC=() +-BASH_ARGV=() ++BASH_ARGC=([0]="1") ++BASH_ARGV=([0]="-C") + BASH_CMDS=() + BASH_LINENO=([0]="0") + BASH_SOURCE=([0]="./configure") ./actypes.at:33: exit code was 1, expected 0 Additionally, the following behavior might complicate a possible solution: https://lists.gnu.org/archive/html/bug-bash/2015-11/msg00059.html So, how to handle Bash 5.0's behavior during make check? Thank you. -- Best regards, Tadeus
