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_8.orig/Makefile duma_2_5_8/Makefile
2 --- duma_2_5_8.orig/Makefile 2007-08-17 09:34:25.000000000 +0200
3 +++ duma_2_5_8/Makefile 2007-09-07 21:50:04.000000000 +0200
16 createconf$(EXEPOSTFIX): createconf.o
17 - $(RMFORCE) createconf$(EXEPOSTFIX)
18 - $(CC) $(CFLAGS) $(DUMA_OPTIONS) createconf.o -o createconf$(EXEPOSTFIX)
19 + $(HOSTCC) $(HOSTCFLAGS) $(DUMA_OPTIONS) createconf.o -o createconf$(EXEPOSTFIX)
21 tstheap$(EXEPOSTFIX): libduma.a tstheap.o
22 - $(RMFORCE) tstheap$(EXEPOSTFIX)
24 # define rules how to build objects for createconf
27 - $(CC) $(CFLAGS) $(DUMA_OPTIONS) -c createconf.c -o $@
28 + $(HOSTCC) $(HOSTCFLAGS) $(DUMA_OPTIONS) -c createconf.c -o $@