[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ksh bug on Tru64 UNIX causes current libtool failure
From: |
Paul Eggert |
Subject: |
Re: ksh bug on Tru64 UNIX causes current libtool failure |
Date: |
Wed, 08 Jun 2005 00:56:43 -0700 |
User-agent: |
Gnus/5.1006 (Gnus v5.10.6) Emacs/21.4 (gnu/linux) |
Ralf Wildenhues <address@hidden> writes:
> * doc/autoconf.texi (Limitations of Builtins) <case>: Mention
> Tru64 ksh pattern matching bug.
Thanks. I installed the following slightly-different patch into
autoconf.
--- autoconf.texi 8 Jun 2005 07:13:50 -0000 1.907
+++ autoconf.texi 8 Jun 2005 07:55:29 -0000 1.908
@@ -10899,6 +10899,16 @@ $
Even with this, SunOS 5.7 ksh matches a backslash if the set contains any
of the characters @samp{|}, @samp{&}, @samp{(}, or @samp{)}.
+Conversely, Tru64 @command{ksh} (circa 2003) erroneously always matches
+a closing parenthesis if not specified in a character class:
+
address@hidden
+$ @kbd{case foo in *\)*) echo fail ;; esac}
+fail
+$ @kbd{case foo in *')'*) echo fail ;; esac}
+fail
address@hidden example
+
Some shells, such as Ash 0.3.8, are confused by an empty
@code{case}/@code{esac}: