[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
strange problem with local bash build -> [a-z] matches A
From: |
Quentin Fennessy |
Subject: |
strange problem with local bash build -> [a-z] matches A |
Date: |
Tue, 23 Jan 2001 10:11:41 -0600 |
I am puzzled with a problem we've found locally. We have bash 2.02 built for
and on Linux and Solaris 2.5.1. When run on certain Solaris 7 systems the
[a-z] pattern matching works incorrectly. When a copy of the same bash is run
on other Solaris 7 systems it works correctly. This is how failure looks:
OS Bash version works/fails?
-- ------------ ------------
Linux2.2 2.02 fails
Linux2.2 2.03 fails
Sol2.5 2.02 works
Sol2.7 2.03 fails sometimes, works others
$ mkdir tmp
$ cd tmp
$ touch A
$ echo [a-z]
[a-z]
$ touch B
$ echo [a-z]
B
$ set|grep BASH
BASH=/tool/pandora/bin/bash
BASH_VERSINFO=([0]="2"
[1]="02"
[2]="1"
[3]="1"
[4]="release"
[5]="sparc-sun-solaris2.5.1")
BASH_VERSION='2.02.1(1)-release'
$ shopt | grep glob
dotglob off
extglob off
nocaseglob off
nullglob off
The strangest part is that [a-z] works on some SOlaris 2.7 systems and fails
on others. I have not been able to figure out what the important difference
is between the two systems.
I cannot find a system dependency in the bash source code that corresponds
to the [a-z] capability. What am I missing?
Thanks.
--
Quentin Fennessy Quentin.Fennessy@amd.com
Office: 512.602.3873
Cell: 512.694.7489
- strange problem with local bash build -> [a-z] matches A,
Quentin Fennessy <=