Allow multi-word "install" command.

Autoconf can determine that the correct install command includes flags,
e.g., "/usr/bin/install -c". When using this as a command, we can't
enclose the value in double-quotes, as that makes some shells use the
whole expression as a filename:

# this is the value returned by autoconf and stored in CT_install
$ ins="/usr/bin/install -c"

# if we call it with quotes, the command is not found
$ "${ins}"
bash: /usr/bin/install -c: No such file or directory

# removing the quotes lets it work as expected
$ ${ins}
/usr/bin/install: missing file operand
Try `/usr/bin/install --help' for more information.

Signed-Off-By: Anthony Foiani <anthony.foiani@gmail.com>

#!@@CT_bash@@

# What we need:

#  - the .config file

# Parse the tools' paths configuration

. "${CT_LIB_DIR}/paths.sh"

# We'll need the stdout later, save it

exec 7>&1

# Parse the common functions

. "${CT_LIB_DIR}/scripts/functions"

# Don't care about any log file

exec >/dev/null

rm -f "${tmp_log_file}"

# Parse the configuration file

. .config.2

# Parse architecture and kernel specific functions

. "${CT_LIB_DIR}/scripts/build/arch/${CT_ARCH}.sh"

. "${CT_LIB_DIR}/scripts/build/kernel/${CT_KERNEL}.sh"

# Build CT_TARGET

CT_DoBuildTargetTuple

# All this for this single echo... :-( Sigh, I'll have to re-arrange things...

echo "${CT_TARGET}" >&7