From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <Neil.Wu@Emerson.com>, <yocto@yoctoproject.org>
Subject: Re: can't find the source code of kernel
Date: Thu, 15 Jan 2015 08:04:37 -0500 [thread overview]
Message-ID: <54B7BAE5.7020700@windriver.com> (raw)
In-Reply-To: <3204FE6663E1F14CAF4CA6928E60C8522763CB6C@USSTLZ-PMSG012.emrsn.org>
On 2015-01-15 5:03 AM, Neil.Wu@Emerson.com wrote:
> Hi ,all
>
> The version of poky is 1.7. I build the linux-yocto is successful .
>
> bitbake linux-yocto
>
> But, why I can’t find the source code of linux in ${WORKDIR}.
It should be there (note: it is about to move in master, but not in 1.7.1).
In WORKDIR, you have "linux" (the source) and linux-$MACHINE-build (the
build).
Bruce
>
> Best wishes
>
> Neil
>
>
>
next prev parent reply other threads:[~2015-01-15 13:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 8:33 [meta-cgl][PATCH] samhain: add new recipe Li xin
2014-12-10 17:28 ` Khem Raj
2014-12-11 0:47 ` Joe MacDonald
2014-12-11 7:21 ` Alexandru Vaduva
2014-12-11 7:51 ` Alexandru Vaduva
2014-12-12 19:53 ` akuster808
2014-12-11 9:35 ` add files to dirctory in packages-split Neil.Wu
2014-12-11 10:04 ` Khem Raj
2014-12-12 1:59 ` Neil.Wu
2014-12-12 2:48 ` Khem Raj
2014-12-12 7:41 ` Neil.Wu
2014-12-17 9:30 ` problem of toolchain install directrory Neil.Wu
2014-12-17 9:46 ` Liviu Gheorghisan
2014-12-18 2:59 ` Neil.Wu
2015-01-15 10:03 ` can't find the source code of kernel Neil.Wu
2015-01-15 13:04 ` Bruce Ashfield [this message]
2015-01-16 1:13 ` Neil.Wu
2015-01-16 4:35 ` Bruce Ashfield
2015-01-20 1:48 ` Neil.Wu
2015-01-20 3:12 ` dependency eglibc resulted in conflicting PREFERRED_PROVIDER entries being found Neil.Wu
2015-01-21 6:59 ` the problem of poky 1.7 when building the custom rootfs Neil.Wu
2014-12-13 18:15 ` [meta-cgl][PATCH] samhain: add new recipe akuster808
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=54B7BAE5.7020700@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=Neil.Wu@Emerson.com \
--cc=yocto@yoctoproject.org \
/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