This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Shell portability question
- From: Enache Adrian <enache at rdslink dot ro>
- To: gcc at gcc dot gnu dot org
- Date: Sun, 7 Sep 2003 21:15:13 +0300
- Subject: Re: Shell portability question
- References: <20030907171218.GA13555@nevyn.them.org>
On Sun, Sep 07, 2003 a.d., Daniel Jacobowitz wrote:
> case $ac_arg in
> -no-create | --no-c* | -n | -no-recursion | --no-r*) continue ;;
> -q | -quiet | --quiet | --quie | --qui | --qu | --q \
> | -silent | --silent | --silen | --sile | --sil)
> continue ;;
> *" "*|*" "*|*[\[\]\~\#\$\^\&\*\(\)\{\}\\\|\;\<\>\?\"\']*)
> ac_arg=`echo "$ac_arg" | sed "s/'/'\\\\\\\\''/g"` ;;
> esac
>
> If ac_arg="'a\1b'", then that case statement matches using bash and doesn't
> using ash. I'm not sure why. But if you add a space to it, then ash eats
try changing it from:
*" "*|*" "*|*[\[\]\~\#\$\^\&\*\(\)\{\}\\\|\;\<\>\?\"\']*)
to:
*" "*|*" "*|*[\[\~\#\$\^\&\*\(\)\{\}\\\|\;\<\>\?\"\']*|*]*)
Regards,
Adi