From: Randy MacLeod <randy.macleod@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>,
harsh jain <harshjain32@gmail.com>,
Kang Kai <kai.kang@windriver.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: Recipe file of Python 2.7.4 of later version
Date: Fri, 19 Sep 2014 10:07:24 -0400 [thread overview]
Message-ID: <541C389C.90202@windriver.com> (raw)
In-Reply-To: <CAJTo0LZZQMBBKRcxpfbOMC2KUWw5ffp=RdBOyymi-wfaq2UL3g@mail.gmail.com>
On 14-09-19 07:37 AM, Burton, Ross wrote:
> On 19 September 2014 12:31, harsh jain <harshjain32@gmail.com> wrote:
>> Python version 2.7.3 is not compatible with AARCH64
>> architecture.Support for AARCH64 is added in 2.7.4 onwards._ctypes.so
>> is not compiled by 2.7.3 python version for AARCH64.
>>
>> 1 ) Can we have recipe file of 2.7.4 or later version. If yes from
>> where i can download.
>> 2 ) There are several other python package which have build dependancy
>> on 2.7.3 version.When I try to install 2.7.4 using custom build recipe
>> file these dependencies give warning message.Is there any global
>> setting in configuration file to solve this issue.
>
> It's past the feature freeze which means we won't merge upgrades, but
> I imagine its fairly simple to identify the patches in 2.7.4 which
> enable aarch64.
Also Kai (CCed) is going to maintain an aarch64 branch on:
http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-contrib
Kai, let us know when your branch is available; hopefully that
will be early next week.
This branch will be continually rebased on master over the next
month or so and then merged to master after 1.7 is branched.
Patches welcome. They should be submitted here on the oe-core
list with an aarch64 tag in the subject line and CCing Kai please.
--
# Randy MacLeod. SMTS, Linux, Wind River
Direct: 613.963.1350
next prev parent reply other threads:[~2014-09-19 14:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 11:31 Recipe file of Python 2.7.4 of later version harsh jain
2014-09-19 11:37 ` Burton, Ross
2014-09-19 14:07 ` Randy MacLeod [this message]
2014-09-19 14:14 ` Burton, Ross
2014-09-22 1:18 ` Kang Kai
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=541C389C.90202@windriver.com \
--to=randy.macleod@windriver.com \
--cc=harshjain32@gmail.com \
--cc=kai.kang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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