Fixed a bug that was introduced when we started deprecating 32bit libraries on 64bit systems.

build/install-build-deps.sh

Index: build/install-build-deps.sh
diff --git a/build/install-build-deps.sh b/build/install-build-deps.sh
index 757c54520fa219cd385b06e4c2cdefed120a718f..382fc11860b1c1df6dc212392ae32e1361b14ddc 100755
--- a/build/install-build-deps.sh
+++ b/build/install-build-deps.sh
@@ -297,6 +297,21 @@ if [ "$(uname -m)" = "x86_64" ]; then
     echo
     echo "Installation complete."
     exit 0
+  else
+    # This conditional statement has been added to deprecate and eventually
+    # remove support for 32bit libraries on 64bit systems. But for the time
+    # being, we still have to support a few legacy systems (e.g. bots), where
+    # this feature is needed.
+    # We only even give the user the option to install these libraries, if
+    # they explicitly requested doing so by setting the --lib32 command line
+    # flag.
+    # And even then, we interactively ask them one more time whether they are
+    # absolutely sure.
+    # In order for that to work, we must reset the ${do_inst_lib32} variable.
+    # There are other ways to achieve the same goal. But resetting the
+    # variable is the best way to document the intended behavior -- and to
+    # allow us to gradually deprecate and then remove the obsolete code.

[Peter Mayo, 2013/09/26 17:53:15]

Ignoring the --no_prompt option?

The "special" bots includes the entire chromeos build fleet.

Going around to each one with a temrinal session option is a surprising fdrain
on time and resources today.

+    do_inst_lib32=
   fi
 
   echo "WARNING"