diff options
| author | John Crispin <john@openwrt.org> | 2014-10-06 04:53:14 +0000 |
|---|---|---|
| committer | John Crispin <john@openwrt.org> | 2014-10-06 04:53:14 +0000 |
| commit | c22bebf6abb7af2e8ccdb65b3b367768c5f051da (patch) | |
| tree | 89347ef08394a2608dd65c49f084cba662a8f95e /BSDmakefile | |
| parent | 74397a14cabecb629d0ecee12d9b1dc9d710ff65 (diff) | |
| download | upstream-c22bebf6abb7af2e8ccdb65b3b367768c5f051da.tar.gz upstream-c22bebf6abb7af2e8ccdb65b3b367768c5f051da.tar.bz2 upstream-c22bebf6abb7af2e8ccdb65b3b367768c5f051da.zip | |
Fix build when TAR_OPTIONS env variable is set
The build system sets a make variable TAR_OPTIONS to the unpacking
command, i.e. "-xf -". Now if an environment variable with the same
name is set, the make variable is automatically exported to the
environment. The make variable is added to the tar command in the
makefile, and tar adds the environment variable. This results in a
command like "tar -c /some/dir -xf - -xf -" which of course doesn't
work. It is also difficult to spot as the second "-xf -" is not
visible on the command line.
I suggest this is fixed by unexporting TAR_OPTIONS as I see no use
of the evironment variable, and it is changed from the original
value anyway.
Signed-off-by: Jan Kardell <jan.kardell@telliq.com>
SVN-Revision: 42794
Diffstat (limited to 'BSDmakefile')
0 files changed, 0 insertions, 0 deletions