config/9364: ./configure does not get along with ash as /bin/sh

[David Welton <da...@apache.org>]

>Number:         9364
>Category:       config
>Synopsis:       ./configure does not get along with ash as /bin/sh
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Fri Jan 04 04:20:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     davidw@apache.org
>Release:        1.3.23-dev
>Organization:
apache
>Environment:
Debian GNU/Linux 'potato', using ash as /bin/sh, version 0.3.8-32.
>Description:
Running ./configure with ash as /bin/sh doesn't work - it doesn't finish creating the configure scripts.  It gives a warning about the SEO variable, amongst other things. I figured that, as portable as Apache is, it had to be a problem with ash, so I filed a bug report against it in Debian, and received this response:

> #!/bin/sh
> 
> bytes=`echo $SEO '\1' | wc -c | awk '{ printf("%s", $1); }'`
> if [ "x$bytes" != "x3" ]; then
>     bytes=`echo -E '\1' | wc -c | awk '{ printf("%s", $1); }'`
>     if [ "x$bytes" != "x3" ]; then
>         echo " + Warning: Your 'echo' command is slightly broken."
>         echo " + It interprets escape sequences per default. We
> 	already"
>         echo " + tried 'echo -E' but had no real success. If errors
> 	occur"
>         echo " + please set the SEO variable in 'configure' manually
> 	to"
>         echo " + the required 'echo' options, i.e. those which force
> 	your"
>         echo " + 'echo' to not interpret escape sequences per
> 	default."
>     else
>         SEO='-E'
>     fi
> fi

This script is not POSIX-compliant.  Please refer to the standard at
www.opengroup.org.
>How-To-Repeat:
Use the script above with ash as /bin/sh
>Fix:
Apparently the configure script has some problems.  It used to work ok.
>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <ap...@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]