Hi Stefan,

On 03/04/2017 23:02, Stefan Agner wrote:

> But then, I don't expect that "/usr/bin/env python" is looking at
> PYTHON.
> 
> As far as I understand env, it just looks up the current environment to
> run its COMMAND argument.

Agree, this is also mz understanding.

> It is helpful as a shebang, but it does not
> seem to make any difference to calling "python" directly (since that
> also just looks up the current environment PATH and executes the first
> python it finds...

Agree - so that is disturbing is the fix calls to "python" inside
Makefile. That means it remains to change:

tools/_libfdt.so: $(patsubst %.o,%.c,$(LIBFDT_OBJS)) tools/libfdt_wrap.c
        LDFLAGS="$(HOSTLDFLAGS)" CFLAGS= python $(srctree)/lib/libfdt/setup.py

to:

tools/_libfdt.so: $(patsubst %.o,%.c,$(LIBFDT_OBJS)) tools/libfdt_wrap.c
        LDFLAGS="$(HOSTLDFLAGS)" CFLAGS= ${PYTHON} 
$(srctree)/lib/libfdt/setup.py


Regards,
Stefano

-- 
=====================================================================
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sba...@denx.de
=====================================================================
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

Reply via email to