Always reference newly created script using full path.

build/install-chroot.sh

 #!/bin/bash -e
 
 # Copyright (c) 2012 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 # This script installs Debian-derived distributions in a chroot environment.
 # It can for example be used to have an accurate 32bit build and test
 # environment when otherwise working on a 64bit machine.
 # N. B. it is unlikely that this script will ever work on anything other than a
@@ skipping 640 matching lines @@
     echo "you now have to install the build dependencies. Do you want me to"
     printf "start the script that does this for you (y/n)? "
     read install_deps
     case "${install_deps}" in
       y|Y)
         echo
         # We prefer running the script in-place, but this might not be
         # possible, if it lives on a network filesystem that denies
         # access to root.
         tmp_script=
-        if ! sudo "${target%bit}" sh -c "[ -x '${script}' ]" >&/dev/null; then
+        if ! sudo /usr/local/bin/"${target%bit}" \
+            sh -c "[ -x '${script}' ]" >&/dev/null; then
           tmp_script="/tmp/${script##*/}"
           cp "${script}" "${tmp_script}"
         fi
         # Some distributions automatically start an instance of the system-
         # wide dbus daemon or of the logging daemon, when installing the Chrome
         # build depencies. This prevents the chroot session from being closed.
         # So, we always try to shut down any running instance of dbus and
         # rsyslog.
         sudo "${target%bit}" sh -c "${script} --no-lib32;
               rc=$?;
@@ skipping 88 matching lines @@
       for i in $(list_all_chroots); do
         sudo "$i" mkdir -p "${dir}/chroot"
       done
       sudo sed -i "s,${HOME}/chroot,${dir}/chroot,g" /etc/schroot/mount-*
       break
     fi
   done
 fi
 
 # Clean up package files
-sudo schroot -c "${target%bit}" -p -- apt-get clean
+sudo schroot -c /usr/local/bin/"${target%bit}" -p -- apt-get clean
 sudo apt-get clean
 
 trap '' INT TERM QUIT HUP
 trap '' EXIT
 
 # Let the user know what we did
 cat <<EOF
 
 
 Successfully installed ${distname} ${arch}
 
-You can run programs inside of the chroot by invoking the "${target%bit}"
-command.
+You can run programs inside of the chroot by invoking the
+"/usr/local/bin/${target%bit}" command.
 
 This command can be used with arguments, in order to just run a single
 program inside of the chroot environment (e.g. "${target%bit} make chrome")
 or without arguments, in order to run an interactive shell session inside
 of the chroot environment.
 
 If you need to run things as "root", you can use "sudo" (e.g. try
 "sudo ${target%bit} apt-get update").
 
 Your home directory is shared between the host and the chroot. But I
 configured "${HOME}/chroot" to be private to the chroot environment.
 You can use it for files that need to differ between environments. This
 would be a good place to store binaries that you have built from your
 source files.
 
 For Chrome, this probably means you want to make your "out" directory a
 symbolic link that points somewhere inside of "${HOME}/chroot".
 
 You still need to run "gclient runhooks" whenever you switch from building
 outside of the chroot to inside of the chroot. But you will find that you
 don't have to repeatedly erase and then completely rebuild all your object
 and binary files.
 
 EOF