I have not come across any "sh/bash" shells that would accept "==".  Since "[" is just syntactical sugar for the program "test" ('/usr/bin/[' is same as /usr/bin/test) doing a "man test" or "man [" shows that only "=" is acceptable.  Bash may have "test" implemented as a built-in for efficiency reasons, although I doubt it since "man bash" doesn't show "[" as a reserved word (so it just runs '/usr/bin/[' like any other program).

On 8/2/07, Craig Hughes <craig@gumstix.com> wrote:
On Aug 2, 2007, at 3:12 PM, Peter Lu wrote:

> Hi,
> These files have simple typos (in revs up to 1491), where "=="
> should be "=":
> ./build_arm_nofpu/wpa_supplicant- 0.5.7/Makefile
> ./toolchain_build_arm_nofpu/uClibc/extra/config/lxdialog/.svn/text-
> base/check- lxdialog.sh.svn-base
> ./toolchain_build_arm_nofpu/uClibc/extra/config/lxdialog/check-
> lxdialog.sh
> How does one go about getting them fixed up in the package or
> patched up in the Gumstix distribution, so that we don't need to
> keep fixing them manually?  Thanks.

I guess it'll work if your shell is bash, but not generally for
POSIX.  The bash manpage says this:

  string1 == string2
               True if the strings are equal.  = may be used in place
of == for strict POSIX compliance.

I'll fix those in the buildroot.


This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
gumstix-users mailing list