From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Adding support for the Rust programming language
Date: Mon, 11 Apr 2016 11:29:05 +0200 [thread overview]
Message-ID: <570B6E61.4030403@mind.be> (raw)
In-Reply-To: <20160411091556.GP3364@tarshish>
On 04/11/16 11:15, Baruch Siach wrote:
> Hi Arnout,
>
> On Mon, Apr 11, 2016 at 11:12:07AM +0200, Arnout Vandecappelle wrote:
>> So, if python is used, please make sure it runs on any python (with full
>> standard library) from python2.4 (RHEL5) to python3.5. That means that using
>> the json standard library module is not an option, since it was introduced
>> only in python 2.6.
>
> The manual (http://nightly.buildroot.org/manual.html#requirement-mandatory)
> currently requires Python 2.6 or newer.
I don't think that that's accurate. Thomas, Jan, I believe you're using RHEL5
with an older python, no?
Regards,
Arnout
--
Arnout Vandecappelle arnout dot vandecappelle at essensium dot com
Senior Embedded Software Architect . . . . . . +32-478-010353 (mobile)
Essensium, Mind division . . . . . . . . . . . . . . http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium . . . . . BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2016-04-11 9:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 20:45 [Buildroot] Adding support for the Rust programming language Eric Le Bihan
2016-04-10 15:57 ` Arnout Vandecappelle
2016-04-11 8:32 ` Thomas Petazzoni
2016-04-11 9:12 ` Arnout Vandecappelle
2016-04-11 9:13 ` Arnout Vandecappelle
2016-04-11 9:31 ` Thomas Petazzoni
2016-04-11 9:15 ` Baruch Siach
2016-04-11 9:29 ` Arnout Vandecappelle [this message]
2016-04-11 11:42 ` Thomas De Schampheleire
2016-04-11 19:03 ` Eric Le Bihan
2016-04-12 20:22 ` Arnout Vandecappelle
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=570B6E61.4030403@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.