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(-)

 # Overall toolchain configuration: paths, jobs, etc...

 menu "Paths and misc options"

 source "config/global/ct-behave.in"

 source "config/global/paths.in"

 source "config/global/download.in"

 source "config/global/extract.in"

 source "config/global/build-behave.in"

 source "config/global/logging.in"

 endmenu