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:
eriktorbjorn 2011-06-18 08:26:55 +02:00
parent b81207a04e
commit 36d720d06b

2
configure vendored
View file

@ -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}"