From: Kang Kai <Kai.Kang@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>,
Randy MacLeod <randy.macleod@windriver.com>
Cc: harsh jain <harshjain32@gmail.com>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: Recipe file of Python 2.7.4 of later version
Date: Mon, 22 Sep 2014 09:18:52 +0800 [thread overview]
Message-ID: <541F78FC.20204@windriver.com> (raw)
In-Reply-To: <CAJTo0LaGKTk=ubSRrv5wsW2eN9qxMOQsB2sKXuRXJUBujym=-g@mail.gmail.com>
On 2014年09月19日 22:14, Burton, Ross wrote:
> On 19 September 2014 15:07, Randy MacLeod <randy.macleod@windriver.com> wrote:
>> 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.
> Great news, thanks Randy and Kai.
>
> (did you mean poky-contrib instead of linux-yocto-contrib?)
I put the git repository at:
git://git.pokylinux.org/poky-contrib kangkai/qemuarm64
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=kangkai/qemuarm64
It is ok to build world except 2 known issues. One depends on valid
linux-yocto configs,
the other one is libunwind issue which should exclude from world for
aarch64. And some
patches from Joe Slater are needed too. Joe has sent them to oe-core. If
not merged, I'll
stage these patches too.
For the kernel support, Zhe has sent the patch to linux-yocto to support
aarch64. Bruce knows this work.
--Kai
>
> Ross
>
>
--
Regards,
Neil | Kai Kang
prev parent reply other threads:[~2014-09-22 1:18 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
2014-09-19 14:14 ` Burton, Ross
2014-09-22 1:18 ` Kang Kai [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=541F78FC.20204@windriver.com \
--to=kai.kang@windriver.com \
--cc=harshjain32@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=randy.macleod@windriver.com \
--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 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.