Hello Wolfgang,
On 30-09-14 10:17, Wolfgang Denk wrote:
Instead of searching for Python2 in $PATH, use the one installed by
the system (i. e. /usr/bin/python2). This prevents failures like
this:
- ./MAKEALL m53evk
Traceback (most recent call last):
File tools/genboardscfg.py, line 19, in
Instead of searching for Python2 in $PATH, use the one installed by
the system (i. e. /usr/bin/python2). This prevents failures like
this:
- ./MAKEALL m53evk
Traceback (most recent call last):
File tools/genboardscfg.py, line 19, in module
import fnmatch
ImportError: No module named
Hi Wolfgang,
On Tue, 30 Sep 2014 10:17:22 +0200
Wolfgang Denk w...@denx.de wrote:
Instead of searching for Python2 in $PATH, use the one installed by
the system (i. e. /usr/bin/python2). This prevents failures like
this:
- ./MAKEALL m53evk
Traceback (most recent call last):
File
Dear Masahiro,
In message 20140930175820.4a3c.aa925...@jp.panasonic.com you wrote:
This happens for example with all but the most recent versions of
Yocto based tool chains (inclusing all currently existing versions of
the ELDK), which provide a python2 binary in SYSROOT/usr/bin/python2,
4 matches
Mail list logo