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 r10231 | lethal | 2005-05-02 09:58:00 -0400 (Mon, 02 May 2005) | 13 lines
3 Likewise, binutils has no idea about any of these new targets either, so we
4 fix that up too.. now we're able to actually build a real toolchain for
5 sh2a_nofpu- and other more ineptly named toolchains (and yes, there are more
6 inept targets than that one, really. Go look, I promise).
8 diff -durN binutils-2.22.orig/configure binutils-2.22/configure
9 --- binutils-2.22.orig/configure 2011-08-14 14:28:15.000000000 +0200
10 +++ binutils-2.22/configure 2011-12-14 19:49:40.284777434 +0100
13 noconfigdirs="$noconfigdirs gprof"
20 diff -durN binutils-2.22.orig/configure.ac binutils-2.22/configure.ac
21 --- binutils-2.22.orig/configure.ac 2011-11-21 12:58:27.000000000 +0100
22 +++ binutils-2.22/configure.ac 2011-12-14 19:49:40.316777436 +0100
25 noconfigdirs="$noconfigdirs gprof"