From: Kang Kai <Kai.Kang@windriver.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>,
"Burton, Ross" <ross.burton@intel.com>
Cc: He Zhe <zhe.he@windriver.com>, Joe Slater <jslater@windriver.com>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] Add machine qemuarm64
Date: Sat, 13 Sep 2014 09:30:09 +0800 [thread overview]
Message-ID: <54139E21.8040308@windriver.com> (raw)
In-Reply-To: <CADkTA4N5K7XecxZNJrgDqvjVzRvGech7pvM0SEyftt7pzf6tvg@mail.gmail.com>
On 2014年09月12日 21:02, Bruce Ashfield wrote:
> On Fri, Sep 12, 2014 at 6:22 AM, Burton, Ross <ross.burton@intel.com> wrote:
>> On 12 September 2014 08:43, Kai Kang <kai.kang@windriver.com> wrote:
>>> There are some packages fail to build with qemuarm64, I will send pathches
>>> for them in another series.
>> I can't build a kernel with MACHINE=qemuarm64:
> Even if this did build, I'm not sure what you'd end up with .. no one
> has sent me
> the linux-yocto machine definition and configuration fragments for qemuarm64
> yet.
Could we make all userspace packages build pass and available for
qemuarm64 first, then deal the kernel?
Zhe He is working on kernel and will give configuration later.
Regards,
Kai
>
> Bruce
>
>> | LINK vmlinux
>> | LD vmlinux.o
>> | aarch64-poky-linux-ld.bfd: cannot find libgcc.a: No such file or directory
>> | aarch64-poky-linux-ld.bfd: cannot find libgcc.a: No such file or directory
>> | make[2]: *** [vmlinux] Error 1
>> | make[1]: *** [sub-make] Error 2
>> | make: *** [all] Error 2
>> | ERROR: oe_runmake failed
>> | WARNING: exit code 1 from a shell command.
>> | ERROR: Function failed: do_compile (log file is located at
>> /data/poky-master/tmp/work/qemuarm64-poky-linux/linux-yocto/3.14.17+gitAUTOINC+a94680bfeb_b85edae6fd-r0/temp/log.do_compile.24366)
>> ERROR: Task 81 (/home/ross/Yocto/poky/meta/recipes-kernel/linux/linux-yocto_3.14.bb,
>> do_compile) failed with exit code '1'
>>
>> I can email build logs if you'd wish.
>>
>> Ross
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>
--
Regards,
Neil | Kai Kang
prev parent reply other threads:[~2014-09-13 1:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 7:43 [PATCH] Add machine qemuarm64 Kai Kang
2014-09-12 7:43 ` Kai Kang
2014-09-12 10:22 ` Burton, Ross
2014-09-12 10:25 ` Kang Kai
2014-09-12 10:29 ` Burton, Ross
2014-09-12 10:32 ` Kang Kai
2014-09-12 13:02 ` Bruce Ashfield
2014-09-13 1:30 ` 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=54139E21.8040308@windriver.com \
--to=kai.kang@windriver.com \
--cc=bruce.ashfield@gmail.com \
--cc=jslater@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
--cc=zhe.he@windriver.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