Re: RFH: bashisms in configure script

[Peter Samuelson <peter@p12n.org>]

[Kurt Roeckx]
> I get alot of them that have:
> possible bashism in ./configure line 22 ($BASH_SOMETHING):
> elif test -n "${BASH_VERSION+set}" && (set -o posix) >/dev/null 2>&1; then
> possible bashism in ./configure line 147 ($BASH_SOMETHING):
>              $as_unset BASH_ENV || test "${BASH_ENV+set}" != set || { BASH_ENV=; export BASH_ENV; }

And more false positives:

possible bashism in ./configure line 44 ($BASH_SOMETHING):
if test -z "$BASH_VERSION$ZSH_VERSION" \
    && (test "X`print -r -- $as_echo`" = "X$as_echo") 2>/dev/null; then
possible bashism in ./configure line 367 (should be >word 2>&1):
    $as_echo "$as_me:${as_lineno-$LINENO}: error: $1" >&$3

Both were produced by autoconf 2.65.

First is a false positive for the same reason Kurt's example is.
Second is a false positive because $3 in this instance is a numbered
file descriptor.

Peter