On 20090120.2203+0100, Andy Johnson <ajohnson@aecno.com> wrote:
The glibc.sh script doesn't handle the glibc versions with
an underscore very well (bash expected integer error). I
have attached a small patch for that. Instead of looking
for "not period" I changed the sense to look for numbers.
I initially tried to make it look for either a period or
an underscore, but that didn't work like I wanted (probably
because I did something wrong).

Original patch modified to be more robust.

/trunk/scripts/build/libc/glibc.sh | 8 4 4 0 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)

--- gdb-6.1.1-dist/readline/configure	2003-05-27 18:29:47.000000000 -0500

+++ gdb-6.1.1/readline/configure	2004-08-09 14:20:23.000000000 -0500

@@ -6249,7 +6249,12 @@

 echo "$as_me:$LINENO: checking for mbstate_t" >&5

+echo $ECHO_N "bash_cv_have_mbstate_t=$bash_cv_have_mbstate_t" >&6

 echo $ECHO_N "checking for mbstate_t... $ECHO_C" >&6

+if test "${bash_cv_have_mbstate_t+set}" != set; then

+  bash_cv_have_mbstate_t=yes

+  echo $ECHO_N "WARNING!! forcing to yes!!! $ECHO_C" >&6

+fi

 if test "${bash_cv_have_mbstate_t+set}" = set; then

   echo $ECHO_N "(cached) $ECHO_C" >&6

 else