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>
1 # Build script for libtool
3 CT_LIBTOOL_VERSION=2.2.6b
5 do_companion_tools_libtool_get() {
6 CT_GetFile "libtool-${CT_LIBTOOL_VERSION}" \
7 {ftp,http}://ftp.gnu.org/gnu/libtool
10 do_companion_tools_libtool_extract() {
11 CT_Extract "libtool-${CT_LIBTOOL_VERSION}"
12 CT_DoExecLog ALL chmod -R u+w "${CT_SRC_DIR}/libtool-${CT_LIBTOOL_VERSION}"
13 CT_Patch "libtool" "${CT_LIBTOOL_VERSION}"
16 do_companion_tools_libtool_build() {
17 CT_DoStep EXTRA "Installing libtool"
18 mkdir -p "${CT_BUILD_DIR}/build-libtool"
19 CT_Pushd "${CT_BUILD_DIR}/build-libtool"
22 "${CT_SRC_DIR}/libtool-${CT_LIBTOOL_VERSION}/configure" \
23 --prefix="${CT_BUILDTOOLS_PREFIX_DIR}"
25 CT_DoExecLog ALL make install