support/scripts/apply-patches: use appropriate TAR
Note that here, it is in fact not really relevant. We only extract a
tarball, and we don't use any "modern" or GNU-only options like
--strip-components. However, for consistency it's better to use the same
tar everywhere.
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
Cc: "Maier, Brandon L Collins" <Brandon.Maier@collins.com>
Reviewed-by: brandon.maier@collins.com
[Arnout: quote TAR="..."]
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
(cherry picked from commit f77d698f83
)
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
This commit is contained in:
parent
9068c31eff
commit
ebc3216762
@ -244,7 +244,7 @@ endif
|
|||||||
INSTALL := $(shell which install || type -p install)
|
INSTALL := $(shell which install || type -p install)
|
||||||
UNZIP := $(shell which unzip || type -p unzip) -q
|
UNZIP := $(shell which unzip || type -p unzip) -q
|
||||||
|
|
||||||
APPLY_PATCHES = PATH=$(HOST_DIR)/bin:$$PATH support/scripts/apply-patches.sh $(if $(QUIET),-s)
|
APPLY_PATCHES = TAR="$(TAR)" PATH=$(HOST_DIR)/bin:$$PATH support/scripts/apply-patches.sh $(if $(QUIET),-s)
|
||||||
|
|
||||||
HOST_CPPFLAGS = -I$(HOST_DIR)/include
|
HOST_CPPFLAGS = -I$(HOST_DIR)/include
|
||||||
HOST_CFLAGS ?= -O2
|
HOST_CFLAGS ?= -O2
|
||||||
|
@ -146,7 +146,7 @@ function scan_patchdir {
|
|||||||
unpackedarchivedir="$builddir/.patches-$(basename $i)-unpacked"
|
unpackedarchivedir="$builddir/.patches-$(basename $i)-unpacked"
|
||||||
rm -rf "$unpackedarchivedir" 2> /dev/null
|
rm -rf "$unpackedarchivedir" 2> /dev/null
|
||||||
mkdir "$unpackedarchivedir"
|
mkdir "$unpackedarchivedir"
|
||||||
tar -C "$unpackedarchivedir" -xaf "${path}/$i"
|
${TAR} -C "$unpackedarchivedir" -xaf "${path}/$i"
|
||||||
scan_patchdir "$unpackedarchivedir"
|
scan_patchdir "$unpackedarchivedir"
|
||||||
else
|
else
|
||||||
apply_patch "$path" "$i"
|
apply_patch "$path" "$i"
|
||||||
|
Loading…
Reference in New Issue
Block a user