diff options
| author | Thomas De Schampheleire <thomas.de_schampheleire@nokia.com> | 2017-02-01 12:27:08 +0100 |
|---|---|---|
| committer | Thomas Petazzoni <thomas.petazzoni@free-electrons.com> | 2017-02-01 22:10:44 +0100 |
| commit | cee060e98e7681c81ced198f078ddc1e7881c9ee (patch) | |
| tree | 4db8df63f2d5ac1ae227483619a65abf56f705fa /package/python-pyzmq/0002-replace-compile_and_run-with-compile_and_forget.patch | |
| parent | 497f69889d21200e55a7519cf64819e9ce6e59cd (diff) | |
| download | buildroot-cee060e98e7681c81ced198f078ddc1e7881c9ee.tar.gz buildroot-cee060e98e7681c81ced198f078ddc1e7881c9ee.zip | |
core infra: make sure apply-patches is called with correct tar
Buildroot has a mechanism to detect a too-old or missing tar program on the
host machine, and builds a custom host-tar if needed. An example situation
is a RHEL5 host machine, where tar is knowingly too old.
The apply-patches script also employs tar, in case the patches come as an
archive. However, tar is called as 'tar' without any absolute path, and the
environment does not point in any way to the possibly custom tar. As a
result, the too-old-tar is called. A particular problem is the flag '-a'
which is missing on e.g. RHEL5.
Previously, this problem went unnoticed: tar would fail, but apply-patches
did not notice it, and the overall return code of the script was 'success'.
However, commit d5ae67b4 added 'set -e' to the script, causing any error to
halt execution of the script with an error.
Fix the problem by adding the Buildroot-built host tools to the PATH when
calling apply-patches.
Signed-off-by: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Diffstat (limited to 'package/python-pyzmq/0002-replace-compile_and_run-with-compile_and_forget.patch')
0 files changed, 0 insertions, 0 deletions
