diff options
| author | Clément Bœsch <u@pkh.me> | 2017-08-14 08:59:11 +0200 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2017-08-20 09:53:13 -0400 |
| commit | 3809e30273e03d762595dbc2a62f3a8398281ec8 (patch) | |
| tree | ce5511e621b0fa490935dfb8506e3c23398e2830 /Makefile | |
| parent | 2629a21e209d91cdb778f43612235ed1f3029488 (diff) | |
| download | u-boot-3809e30273e03d762595dbc2a62f3a8398281ec8.tar.gz u-boot-3809e30273e03d762595dbc2a62f3a8398281ec8.tar.bz2 u-boot-3809e30273e03d762595dbc2a62f3a8398281ec8.zip | |
Makefile: honor PYTHON configuration properly
On some systems `python` is `python3` (for instance, Archlinux). The
`PYTHON` variable can be used to point to `python2` to have a successful
build.
The use of `PYTHON` is currently limited in the Makefile and needs to be
extended in other places:
First, pylibfdt is required to be a Python 2 binding (binman imports
pylibfdt and is only compatible Python 2), so its setup.py needs to be
called accordingly. An alternative would be to change the libfdt
setup.py shebang to python2, but the binding is actually portable. Also,
it would break on system where there is no such thing as `python2`.
Secondly, the libfdt import checks need to be done against Python 2 as
well since the Python 2 compiled modules (in this case _libdft.so) can
not be imported from Python 3.
Note on the libfdt imports: "@if ! PYTHONPATH=tools $(PYTHON) -c 'import
libfdt'; then..." is probably simpler than the currently sub-optimal
pipe.
Reviewed-by: Jonathan Gray <jsg@jsg.id.au>
Diffstat (limited to 'Makefile')
| -rw-r--r-- | Makefile | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -1379,7 +1379,7 @@ $(timestamp_h): $(srctree)/Makefile FORCE $(call filechk,timestamp.h) checkbinman: tools - @if ! ( echo 'import libfdt' | ( PYTHONPATH=tools python )); then \ + @if ! ( echo 'import libfdt' | ( PYTHONPATH=tools $(PYTHON) )); then \ echo >&2; \ echo >&2 '*** binman needs the Python libfdt library.'; \ echo >&2 '*** Either install it on your system, or try:'; \ |