On Tue, Aug 17, 2021 at 01:02:06PM +0200, Osipov, Michael (LDA IT PLM) wrote:
> this is basically the same issue as I reported in readline:
> https://lists.gnu.org/archive/html/bug-readline/2021-08/msg00000.html
As Chet said in that message, you have misinterpreted the POSIX
documentation.
> The bad hunk seems not to be POSIX shell compliant. Both vars are set for me
> on HP-UX because the expansion is incomplete. According to [1] it has to be
> $(GCC:+..} and not $(GCC+..}. I have changed ./configure locally and it
> works with /bin/sh.
What version of HP-UX? What is the actual error you're getting?
I only have access to certain older versions of HP-UX, but I don't
see what you're claiming.
# exec /bin/sh
# uname -a
HP-UX minea B.11.11 U 9000/785 4239047153 unlimited-user license
# GCC=gcc
# echo "[${GCC+-foo}]"
[-foo]
# unset GCC
# echo "[${GCC+-foo}]"
[]
#
>From your email, my first guess was that you thought there was a parsing
ambiguity when the +- characters appeared together, but I cannot reproduce
any problem. Please give more detail.
(P.S. you also have typos in your email. You've got an open left paren
which is "matched" by a closing right curly brace. If you actually
edited some file and introduced that typo, that might account for whatever
error you're seeing. If on the other hand there really is a mismatched
paren-brace error in one of bash's source code files, that would be a
real bug.)
