From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: James Abernathy <jfabernathy@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Developer Manual Appendix B example
Date: Thu, 12 Jan 2012 21:54:31 -0500 [thread overview]
Message-ID: <4F0F9CE7.9010505@windriver.com> (raw)
In-Reply-To: <CANFv2E=kWehG23TsZV76=W7o7GbhbZok2MtacVrOZUmsb+xA0g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1965 bytes --]
On 12-01-12 09:50 PM, James Abernathy wrote:
> I'm trying to do the Developer Manual Appendix B example exactly as
> written only changing the path to my home directory. When I get to
> B.1.8.3, bitbake after patching the kernel calibrate.c and modifiing
> the path to the local git repository for linux-yocto, I get an error
> on the build. The log file of the error is below:
Funny how things tend to arrive in bunches. We just discussed this today
on the
list. The meta-kernel-dev layer is tied to master, and causes this
problem when
used with edison. And that's what you are seeing here. I'm going to
create a edison
branch for meta-kernel-dev to match up the tool SRCREVs.
In the meantime, if you remove the kern-tools-native_git.bbappend from
the meta-kernel-dev
layer, the AUTOREV setting will be removed, and you won't pull in tools
that are too
new for the matching kernel.
Cheers,
Bruce
>
> [INFO] doing kernel configme
> [INFO] Branch yocto/standard/common-pc/base used by common-pc-standard.scc
> [INFO] collecting configs in ./meta/meta-series
> mv: cannot stat
> `/home/jim/poky/build/tmp/work/qemux86-poky-linux/linux-yocto-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+72671808fdbe69a9fe03fd8f094e7c59da04a28c-r2/linux-qemux86-standard-build/.tmp.config*':
> No such file or directory
> creation of pre-processed config data failed
> config of yocto/standard/common-pc/base (common-pc-standard.scc) failed
> ERROR: Function 'do_kernel_configme' failed (see
> /home/jim/poky/build/tmp/work/qemux86-poky-linux/linux-yocto-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+72671808fdbe69a9fe03fd8f094e7c59da04a28c-r2/temp/log.do_kernel_configme.15214
> for further information)
>
> Any help would be appreciated.
>
> Jim A
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
[-- Attachment #2: Type: text/html, Size: 3125 bytes --]
next prev parent reply other threads:[~2012-01-13 2:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 2:50 Developer Manual Appendix B example James Abernathy
2012-01-13 2:54 ` Bruce Ashfield [this message]
2012-01-13 3:59 ` James Abernathy
2012-01-13 4:03 ` Brian Hutchinson
2012-01-13 13:16 ` Rifenbark, Scott M
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=4F0F9CE7.9010505@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=jfabernathy@gmail.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 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.