CONFIGURE: Use = to test for string equality, not ==
I think this is correct. It's consistent with how it's done in other places in the configure script, and it silences a bunch of "unexpected operator" warnings for me.
This commit is contained in:
parent
b81207a04e
commit
36d720d06b
1 changed files with 1 additions and 1 deletions
2
configure
vendored
2
configure
vendored
|
@ -65,7 +65,7 @@ get_var() {
|
|||
# Add an engine: id name build subengines
|
||||
add_engine() {
|
||||
_engines="${_engines} ${1}"
|
||||
if test "${3}" == "no" ; then
|
||||
if test "${3}" = "no" ; then
|
||||
set_var _wip_engines "${_wip_engines} ${1}"
|
||||
fi
|
||||
set_var _engine_${1}_name "${2}"
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue