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>
3 menu "Operating System"
5 # Config option used throughout the config and code to determine wether
6 # we have a kernel or not (there might be different bare metal stuff)...
13 # Each target OS (aka kernel) that support shared libraries can select
14 # this, so the user can decide whether or not to build a shared library
16 config KERNEL_SUPPORTS_SHARED_LIBS
25 source "config.gen/kernel.in"
27 comment "Common kernel options"
31 prompt "Build shared libraries"
32 depends on KERNEL_SUPPORTS_SHARED_LIBS
35 Say 'y' here, unless you don't want shared libraries.
37 You might not want shared libraries if you're building for a target that
38 don't support it (maybe some nommu targets, for example, or bare metal).
40 source "config.gen/kernel.in.2"