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 diff -durN duma_2_5_15.orig/GNUmakefile duma_2_5_15/GNUmakefile
2 --- duma_2_5_15.orig/GNUmakefile 2008-08-03 21:22:38.000000000 +0200
3 +++ duma_2_5_15/GNUmakefile 2009-06-19 15:32:23.000000000 +0200
17 createconf$(EXEPOSTFIX): createconf.o
18 - $(RMFORCE) createconf$(EXEPOSTFIX)
19 - $(CC) $(CFLAGS) $(DUMA_OPTIONS) createconf.o -o createconf$(EXEPOSTFIX)
20 + $(HOSTCC) $(HOSTCFLAGS) $(DUMA_OPTIONS) createconf.o -o createconf$(EXEPOSTFIX)
22 tstheap$(EXEPOSTFIX): libduma.a tstheap.o
23 - $(RMFORCE) tstheap$(EXEPOSTFIX)
25 # define rules how to build objects for createconf
28 - $(CC) $(CFLAGS) $(DUMA_OPTIONS) -c createconf.c -o $@
29 + $(HOSTCC) $(HOSTCFLAGS) $(DUMA_OPTIONS) -c createconf.c -o $@