public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jeroen Hofstee <dasuboot@myspectrum.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] Python subprocess module missing in multiconfig.py
Date: Thu, 07 Aug 2014 22:37:52 +0200	[thread overview]
Message-ID: <53E3E3A0.60407@myspectrum.nl> (raw)
In-Reply-To: <201408072214.14351.marex@denx.de>

Hello Marex, Tom,

On 07-08-14 22:14, Marek Vasut wrote:
> <snip>
>> Well putting on my small, tiny OE user head, you need to spell out
>> every python-module you use. To make it a bit more funny there are
>> likely grouped, so don't be surprised this is python-system or something.
>> I am in the impression the nativesdk uses the same recipes where
>> possible, so hence needs to be rebuild with explicit DEPENDS (unless
>> you got luckily that a recipe before u-boot included it.) Anyway there
>> are a lot more people on the list who know this a lot better, Marex?
> Thanks for CCing me.
>
> I sent a patch to OE-core to ship the python modules. This is a problem with the
> Yocto Qt SDK toolchain in general and you can track the mayhem at [1]. There
> will likely be ELDK 5.5.3 once this is all settled.
>
> btw. you should update to ELDK 5.5.2 in the first place, since the compiler in
> Yocto 1.5.0 did have trouble with code generation [2], [3].
>
> [1] http://lists.openembedded.org/pipermail/openembedded-core/2014-
> August/095470.html
> [2] http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58854
> [3]http://lists.openembedded.org/pipermail/openembedded-core/2014-
> February/089489.html
>

A bit of topic, beside the toolchain problems, aren't these
dependencies of the u-boot recipe? The native sdk will pick
them up if any machine needs them (at least in my setup).
Besides of that, do we really want so much dependencies
for u-boot what used to be sed, awk.. and uh find perhaps?
Is all of this needed to just compile u-boot?

	nativesdk-python-core \
	nativesdk-python-textutils \
	nativesdk-python-sqlite3 \
	nativesdk-python-pickle \
	nativesdk-python-logging \
	nativesdk-python-elementtree \
	nativesdk-python-curses \
	nativesdk-python-compile \
	nativesdk-python-compiler \
	nativesdk-python-fcntl \
	nativesdk-python-shell \
	nativesdk-python-misc \
	nativesdk-python-multiprocessing \
	nativesdk-python-subprocess \
	nativesdk-python-xmlrpc \
	nativesdk-python-netclient \
	nativesdk-python-netserver \
	nativesdk-python-distutils \
	nativesdk-python-unixadmin \
	nativesdk-python-compression \
	nativesdk-python-json \
	nativesdk-python-unittest \
	nativesdk-python-mmap \
	nativesdk-python-difflib \
	nativesdk-python-pprint \
	nativesdk-python-git \
	nativesdk-python-pkgutil \


Regards,
Jeroen

  reply	other threads:[~2014-08-07 20:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-07 16:11 [U-Boot] Python subprocess module missing in multiconfig.py david at plentovichdesign.com
2014-08-07 19:08 ` Tom Rini
2014-08-07 19:37   ` Jeroen Hofstee
2014-08-07 19:43     ` Tom Rini
2014-08-07 20:02       ` Jeroen Hofstee
2014-08-07 20:04         ` Jeroen Hofstee
2014-08-07 20:14         ` Marek Vasut
2014-08-07 20:37           ` Jeroen Hofstee [this message]
2014-08-07 21:52             ` Marek Vasut
2014-08-08 22:16               ` Jeroen Hofstee
2014-08-09 12:52                 ` Marek Vasut

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=53E3E3A0.60407@myspectrum.nl \
    --to=dasuboot@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