I know I'm in the dark ages with Bash 3.1.17, but RHEL is popular enough, so it should work for there. In fact, bashdb seems to work just fine, but the configure command barfs. I patched the config file as follows:
--- configure 2008-11-15 18:51:28.000000000 +0100 +++ configure.orig 2008-11-28 16:44:37.000000000 +0100 @@ -2799,7 +2799,7 @@ bash_major=`$SH_PROG -c 'echo ${BASH_VERSINFO[0]}'` bash_minor=`$SH_PROG -c 'echo ${BASH_VERSINFO[1]}'` case "${bash_major}.${bash_minor}" in - '4.0'|'3.2') + '4.0'|'3.2'*|'3.1'*) ;; *) { echo "$as_me:$LINENO: WARNING: You have Bash $bash_version installed." >&5
You ran the regression tests ("make check") and all of those worked correctly?
The reason 3.1 was not mentioned is merely because I didn't do testing under bash 3.1. However it if works, I'll include it.
I've just changed the CVS source to allow bash 3.1. Of course, it's possible I messed this up somehow so please double check the change.
Log in to post a comment.
I know I'm in the dark ages with Bash 3.1.17, but RHEL is popular enough, so it should work for there. In fact, bashdb seems to work just fine, but the configure command barfs. I patched the config file as follows:
--- configure 2008-11-15 18:51:28.000000000 +0100
+++ configure.orig 2008-11-28 16:44:37.000000000 +0100
@@ -2799,7 +2799,7 @@
bash_major=`$SH_PROG -c 'echo ${BASH_VERSINFO[0]}'`
bash_minor=`$SH_PROG -c 'echo ${BASH_VERSINFO[1]}'`
case "${bash_major}.${bash_minor}" in
- '4.0'|'3.2')
+ '4.0'|'3.2'*|'3.1'*)
;;
*)
{ echo "$as_me:$LINENO: WARNING: You have Bash $bash_version installed." >&5
You ran the regression tests ("make check") and all of those worked correctly?
The reason 3.1 was not mentioned is merely because I didn't do testing under bash 3.1. However it if works, I'll include it.
I've just changed the CVS source to allow bash 3.1. Of course, it's possible I messed this up somehow so please double check the change.