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 --- glibc-2.13/sysdeps/unix/sysv/linux/kernel-features.h 2010-07-27 14:34:39.000000000 +0300
2 +++ glibc-2.13/sysdeps/unix/sysv/linux/kernel-features.h.new 2011-03-10 18:54:37.686795979 +0200
4 the code. On PPC they were introduced in 2.6.17-rc1,
5 on SH in 2.6.19-rc1. */
6 #if __LINUX_KERNEL_VERSION >= 0x020611 \
7 - && (!defined __sh__ || __LINUX_KERNEL_VERSION >= 0x020613)
8 + && (!defined __sh__ || __LINUX_KERNEL_VERSION >= 0x020613) \
9 + && (!defined __alpha__)
10 # define __ASSUME_ATFCTS 1