From: Jeroen Hofstee <jeroen@myspectrum.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH] genboardscfg.py: use Python2 from default path
Date: Sun, 12 Oct 2014 17:46:55 +0200 [thread overview]
Message-ID: <543AA26F.4090804@myspectrum.nl> (raw)
In-Reply-To: <1412065042-572-1-git-send-email-wd@denx.de>
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 <module>
> import fnmatch
> ImportError: No module named fnmatch
> Failed to generate boards.cfg
>
> 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,
> but do not include the "fnmatch" module.
>
> By using the system installed Python interpreter, the user is able to
> install any missing modules himself, without need to patch and rebuild
> the whole tool chain.
>
>
Well lets start with, is this an issue at all? I never run MAKEALL
from oe as it taints my environment. Thanks to Masahiro, deployment
should not depend on python at all. Developers can install the required
python version themselves, even if they don't have root priviliges, since
env can pick it up.
Furthermore the tool chains are there to provide the needed tools, so to
insist on using the host version is exactly the opposite of what they want
to achieve.
Regards,
Jeroen
prev parent reply other threads:[~2014-10-12 15:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 8:17 [U-Boot] [RFC PATCH] genboardscfg.py: use Python2 from default path Wolfgang Denk
2014-09-30 8:58 ` Masahiro Yamada
2014-09-30 11:36 ` Wolfgang Denk
2014-10-12 15:46 ` Jeroen Hofstee [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=543AA26F.4090804@myspectrum.nl \
--to=jeroen@myspectrum.nl \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox