On Tue, Aug 17, 2021 at 5:40 PM Greg Wooledge <g...@wooledge.org> wrote:
> I'm still wondering what issue the OP is actually seeing. If they claim
> that changing ${GCC+-stuff} to ${GCC:+-stuff} in some file fixes things,
> and if they also claim that *something* is setting the GCC variable to
> the empty string rather than unsetting it, then perhaps it's not a
> syntactic error at all, but rather a logical error.
>
I have this in the configure script:
if test $ac_compiler_gnu = yes; then
GCC=yes
else
GCC=
fi
I don't know which part of autoconf exactly generates it. They also
mentioned it in this message:
https://lists.gnu.org/archive/html/bug-readline/2021-08/msg00002.html
> Either the thing that's setting GCC to the empty string ought to be
> changed to unset GCC, or else the ${GCC+-stuff} check ought to be changed
> to ${GCC:+-stuff} (at the risk of breaking Bourne shell compatibility,
> if we care about that).
>
As far as I can see, that's actually already fixed in the devel branch:
https://git.savannah.gnu.org/cgit/bash.git/tree/configure.ac?h=devel#n417
and
https://git.savannah.gnu.org/cgit/bash.git/tree/CWRU/CWRU.chlog?h=devel#n1503
