Discussion:
Build error while following Appendix A. Yocto Project Development manual
(too old to reply)
James Abernathy
2011-11-01 18:37:15 UTC
Permalink
I tried to duplicate the Yocto Project Decelopment Manual Appendix A build
of a Crownbay NOEMGD image, no changes just dulicate the instructions.
This is using the latest Yocto 1.1. I did get a long way down the line,
but had a fatal error in the last 2 steps.


The only change I had to make was related to A.5.2.4. The commit string
for the SRCREV_meta_pn was different on the
git.yoctoproject.org/cgit/cgifor the Meta commit so I used what I
found online. The first section of
126 task completed without error. The next section of 4394 tasks failed on
4393. Not sure if the error is obvious, but I wanted to run it by someone.
Console error log below:

NOTE: package core-image-sato-1.0-r0: task do_bootimg: Started
ERROR: Function 'build_boot_bin' failed (see
/home/jim/poky/yocto-build/tmp/work/mymachine-poky-linux/core-image-sato-1.0-r0/temp/log.do_bootimg.31418
for further information)
ERROR: Logfile of failure stored in:
/home/jim/poky/yocto-build/tmp/work/mymachine-poky-linux/core-image-sato-1.0-r0/temp/log.do_bootimg.31418
Log data follows:
| install: cannot stat
`/home/jim/poky/yocto-build/tmp/sysroots/mymachine/kernel/bzImage': No such
file or directory
| ERROR: Function 'build_boot_bin' failed (see
/home/jim/poky/yocto-build/tmp/work/mymachine-poky-linux/core-image-sato-1.0-r0/temp/log.do_bootimg.31418
for further information)
NOTE: package core-image-sato-1.0-r0: task do_bootimg: Failed
ERROR: Task 9 (/home/jim/poky/meta/recipes-sato/images/core-image-sato.bb,
do_bootimg) failed with exit code '1'
ERROR: '/home/jim/poky/meta/recipes-sato/images/core-image-sato.bb' failed
***@jim-ubuntu-10:~/poky/yocto-build$
Tom Zanussi
2011-11-01 19:40:49 UTC
Permalink
Hi,
Post by James Abernathy
I tried to duplicate the Yocto Project Decelopment Manual Appendix A
build of a Crownbay NOEMGD image, no changes just dulicate the
instructions. This is using the latest Yocto 1.1. I did get a long
way down the line, but had a fatal error in the last 2 steps.
The only change I had to make was related to A.5.2.4. The commit
string for the SRCREV_meta_pn was different on the
git.yoctoproject.org/cgit/cgi for the Meta commit so I used what I
found online. The first section of 126 task completed without error.
The next section of 4394 tasks failed on 4393. Not sure if the error
is obvious, but I wanted to run it by someone. Console error log
Hmm, not sure what's going on here - I'm sure this example was verified
several times, but just to make sure, what you're doing is going through
'Appendix A. BSP Development Example' verbatim and getting this?

The SRCREVs in either case look ok for this, so that shouldn't be the
problem...

But let me go over the steps myself and see what I come up with - will
let you know either way...

Tom
Post by James Abernathy
NOTE: package core-image-sato-1.0-r0: task do_bootimg: Started
ERROR: Function 'build_boot_bin' failed
(see /home/jim/poky/yocto-build/tmp/work/mymachine-poky-linux/core-image-sato-1.0-r0/temp/log.do_bootimg.31418 for further information)
ERROR: Logfile of failure stored
in: /home/jim/poky/yocto-build/tmp/work/mymachine-poky-linux/core-image-sato-1.0-r0/temp/log.do_bootimg.31418
| install: cannot stat
`/home/jim/poky/yocto-build/tmp/sysroots/mymachine/kernel/bzImage': No
such file or directory
| ERROR: Function 'build_boot_bin' failed
(see /home/jim/poky/yocto-build/tmp/work/mymachine-poky-linux/core-image-sato-1.0-r0/temp/log.do_bootimg.31418 for further information)
NOTE: package core-image-sato-1.0-r0: task do_bootimg: Failed
ERROR: Task 9
(/home/jim/poky/meta/recipes-sato/images/core-image-sato.bb,
do_bootimg) failed with exit code '1'
ERROR: '/home/jim/poky/meta/recipes-sato/images/core-image-sato.bb' failed
James Abernathy
2011-11-01 19:48:03 UTC
Permalink
Just to clear up the basics, Prior to following Appendix A verbatim, I did
the following
1. install prerequisites from GS guide
2. git clone git://git.yoctoproject.org/poky
3. cd poky
4. git clone git://git.yoctoproject.org/meta-intel.git

I did not install the poky-extras. I assumed it only had to be installed if
you installed the kernel source for modification like in Appendix b

Jim a
Post by Tom Zanussi
Hi,
Post by James Abernathy
I tried to duplicate the Yocto Project Decelopment Manual Appendix A
build of a Crownbay NOEMGD image, no changes just dulicate the
instructions. This is using the latest Yocto 1.1. I did get a long
way down the line, but had a fatal error in the last 2 steps.
The only change I had to make was related to A.5.2.4. The commit
string for the SRCREV_meta_pn was different on the
git.yoctoproject.org/cgit/cgi for the Meta commit so I used what I
found online. The first section of 126 task completed without error.
The next section of 4394 tasks failed on 4393. Not sure if the error
is obvious, but I wanted to run it by someone. Console error log
Hmm, not sure what's going on here - I'm sure this example was verified
several times, but just to make sure, what you're doing is going through
'Appendix A. BSP Development Example' verbatim and getting this?
The SRCREVs in either case look ok for this, so that shouldn't be the
problem...
But let me go over the steps myself and see what I come up with - will
let you know either way...
Tom
Post by James Abernathy
NOTE: package core-image-sato-1.0-r0: task do_bootimg: Started
ERROR: Function 'build_boot_bin' failed
(see
/home/jim/poky/yocto-build/tmp/work/mymachine-poky-linux/core-image-sato-1.0-r0/temp/log.do_bootimg.31418
for further information)
Post by James Abernathy
ERROR: Logfile of failure stored
/home/jim/poky/yocto-build/tmp/work/mymachine-poky-linux/core-image-sato-1.0-r0/temp/log.do_bootimg.31418
Post by James Abernathy
| install: cannot stat
`/home/jim/poky/yocto-build/tmp/sysroots/mymachine/kernel/bzImage': No
such file or directory
| ERROR: Function 'build_boot_bin' failed
(see
/home/jim/poky/yocto-build/tmp/work/mymachine-poky-linux/core-image-sato-1.0-r0/temp/log.do_bootimg.31418
for further information)
Post by James Abernathy
NOTE: package core-image-sato-1.0-r0: task do_bootimg: Failed
ERROR: Task 9
(/home/jim/poky/meta/recipes-sato/images/core-image-sato.bb,
do_bootimg) failed with exit code '1'
ERROR: '/home/jim/poky/meta/recipes-sato/images/core-image-sato.bb' failed
Tom Zanussi
2011-11-01 19:55:41 UTC
Permalink
Post by James Abernathy
Just to clear up the basics, Prior to following Appendix A verbatim, I
did the following
1. install prerequisites from GS guide
2. git clone git://git.yoctoproject.org/poky
3. cd poky
4. git clone git://git.yoctoproject.org/meta-intel.git
I did not install the poky-extras. I assumed it only had to be
installed if you installed the kernel source for modification like in
Appendix b
Yeah, normally, assuming you're using an existing kernel branch. But
you didn't get a build error for the kernel, so I'm assuming that's the
case.

Tom
Post by James Abernathy
Jim a
Hi,
Post by James Abernathy
I tried to duplicate the Yocto Project Decelopment Manual
Appendix A
Post by James Abernathy
build of a Crownbay NOEMGD image, no changes just dulicate
the
Post by James Abernathy
instructions. This is using the latest Yocto 1.1. I did
get a long
Post by James Abernathy
way down the line, but had a fatal error in the last 2
steps.
Post by James Abernathy
The only change I had to make was related to A.5.2.4. The
commit
Post by James Abernathy
string for the SRCREV_meta_pn was different on the
git.yoctoproject.org/cgit/cgi for the Meta commit so I used
what I
Post by James Abernathy
found online. The first section of 126 task completed
without error.
Post by James Abernathy
The next section of 4394 tasks failed on 4393. Not sure if
the error
Post by James Abernathy
is obvious, but I wanted to run it by someone. Console error
log
Hmm, not sure what's going on here - I'm sure this example was verified
several times, but just to make sure, what you're doing is going through
'Appendix A. BSP Development Example' verbatim and getting this?
The SRCREVs in either case look ok for this, so that shouldn't be the
problem...
But let me go over the steps myself and see what I come up with - will
let you know either way...
Tom
Started
Post by James Abernathy
ERROR: Function 'build_boot_bin' failed
(see /home/jim/poky/yocto-build/tmp/work/mymachine-poky-linux/core-image-sato-1.0-r0/temp/log.do_bootimg.31418 for further information)
Post by James Abernathy
ERROR: Logfile of failure stored
in: /home/jim/poky/yocto-build/tmp/work/mymachine-poky-linux/core-image-sato-1.0-r0/temp/log.do_bootimg.31418
Post by James Abernathy
| install: cannot stat
`/home/jim/poky/yocto-build/tmp/sysroots/mymachine/kernel/bzImage': No
Post by James Abernathy
such file or directory
| ERROR: Function 'build_boot_bin' failed
(see /home/jim/poky/yocto-build/tmp/work/mymachine-poky-linux/core-image-sato-1.0-r0/temp/log.do_bootimg.31418 for further information)
Failed
Post by James Abernathy
ERROR: Task 9
(/home/jim/poky/meta/recipes-sato/images/core-image-sato.bb,
do_bootimg) failed with exit code '1'
'/home/jim/poky/meta/recipes-sato/images/core-image-sato.bb'
Post by James Abernathy
failed
James Abernathy
2011-11-01 20:04:15 UTC
Permalink
The odd thing is not only is the bzImage file is missing, but also is the
whole kernel directory that bzImage is supposed to be locate in.

/home/jim/poky/yocto-build/tmp/sysroots/mymachine/kernel/bzImage

In the sysroots/mymachine/ directory there is only:

lib/
shlibs/
usr/

Jim A
Post by Tom Zanussi
Post by James Abernathy
Just to clear up the basics, Prior to following Appendix A verbatim, I
did the following
1. install prerequisites from GS guide
2. git clone git://git.yoctoproject.org/poky
3. cd poky
4. git clone git://git.yoctoproject.org/meta-intel.git
I did not install the poky-extras. I assumed it only had to be
installed if you installed the kernel source for modification like in
Appendix b
Yeah, normally, assuming you're using an existing kernel branch. But
you didn't get a build error for the kernel, so I'm assuming that's the
case.
Tom
Post by James Abernathy
Jim a
Hi,
Post by James Abernathy
I tried to duplicate the Yocto Project Decelopment Manual
Appendix A
Post by James Abernathy
build of a Crownbay NOEMGD image, no changes just dulicate
the
Post by James Abernathy
instructions. This is using the latest Yocto 1.1. I did
get a long
Post by James Abernathy
way down the line, but had a fatal error in the last 2
steps.
Post by James Abernathy
The only change I had to make was related to A.5.2.4. The
commit
Post by James Abernathy
string for the SRCREV_meta_pn was different on the
git.yoctoproject.org/cgit/cgi for the Meta commit so I used
what I
Post by James Abernathy
found online. The first section of 126 task completed
without error.
Post by James Abernathy
The next section of 4394 tasks failed on 4393. Not sure if
the error
Post by James Abernathy
is obvious, but I wanted to run it by someone. Console error
log
Hmm, not sure what's going on here - I'm sure this example was verified
several times, but just to make sure, what you're doing is
going through
'Appendix A. BSP Development Example' verbatim and getting this?
The SRCREVs in either case look ok for this, so that shouldn't be the
problem...
But let me go over the steps myself and see what I come up with - will
let you know either way...
Tom
Started
Post by James Abernathy
ERROR: Function 'build_boot_bin' failed
(see
/home/jim/poky/yocto-build/tmp/work/mymachine-poky-linux/core-image-sato-1.0-r0/temp/log.do_bootimg.31418
for further information)
Post by James Abernathy
Post by James Abernathy
ERROR: Logfile of failure stored
/home/jim/poky/yocto-build/tmp/work/mymachine-poky-linux/core-image-sato-1.0-r0/temp/log.do_bootimg.31418
Post by James Abernathy
Post by James Abernathy
| install: cannot stat
`/home/jim/poky/yocto-build/tmp/sysroots/mymachine/kernel/bzImage': No
Post by James Abernathy
Post by James Abernathy
such file or directory
| ERROR: Function 'build_boot_bin' failed
(see
/home/jim/poky/yocto-build/tmp/work/mymachine-poky-linux/core-image-sato-1.0-r0/temp/log.do_bootimg.31418
for further information)
Post by James Abernathy
Failed
Post by James Abernathy
ERROR: Task 9
(/home/jim/poky/meta/recipes-sato/images/core-image-sato.bb,
do_bootimg) failed with exit code '1'
'/home/jim/poky/meta/recipes-sato/images/core-image-sato.bb'
Post by James Abernathy
failed
Tom Zanussi
2011-11-02 00:45:38 UTC
Permalink
Hi James,

I'm still not sure what happened in your case to cause this problem, but
I just went through the Appendix A example pretty much as described, and
got a good build out of it. There was one particular part of the
example that wasn't exactly clear and that could definitely cause some
build problems if you did it incorrectly (the section that makes changes
to linux-yocto_3.0.bbappend, which in the example has a custom branch in
the .bbappend file, but has the explanation using atom-pc).

I'll work with Scott to make sure that part gets cleaned up, along with
the other comments that should get pulled in, but in the meantime, I
captured the steps I used below, which should work in the same way for
you.

***@elmorro:/usr/local/dev/yocto$ mkdir bsp-test; cd bsp-test
***@elmorro:/usr/local/dev/yocto/bsp-test$ git clone git://git.yoctoproject.org/poky
***@elmorro:/usr/local/dev/yocto/bsp-test$ cd poky
***@elmorro:/usr/local/dev/yocto/bsp-test/poky$ git checkout -b edison origin/edison
***@elmorro:/usr/local/dev/yocto/bsp-test/poky$ git clone git://git.yoctoproject.org/meta-intel.git
***@elmorro:/usr/local/dev/yocto/bsp-test/poky$ cd meta-intel
***@elmorro:/usr/local/dev/yocto/bsp-test/poky/meta-intel$ git checkout -b edison origin/edison
***@elmorro:/usr/local/dev/yocto/bsp-test/poky/meta-intel$ cp -a meta-crownbay/ meta-mymachine
***@elmorro:/usr/local/dev/yocto/bsp-test/poky/meta-intel$ rm meta-mymachine/conf/machine/crownbay.conf
***@elmorro:/usr/local/dev/yocto/bsp-test/poky/meta-intel$ mv meta-mymachine/conf/machine/crownbay-noemgd.conf meta-mymachine/conf/machine/mymachine.conf
***@elmorro:/usr/local/dev/yocto/bsp-test/poky/meta-intel$ rm -rf meta-mymachine/recipes-bsp/formfactor/formfactor/crownbay/
***@elmorro:/usr/local/dev/yocto/bsp-test/poky/meta-intel$ mv meta-mymachine/recipes-bsp/formfactor/formfactor/crownbay-noemgd meta-mymachine/recipes-bsp/formfactor/formfactor/mymachine
***@elmorro:/usr/local/dev/yocto/bsp-test/poky/meta-intel$ rm -rf meta-mymachine/recipes-graphics/xorg-xserver/xserver-xf86-config/crownbay

----
The Developer's Manual seems to want to base the BSP on atom-pc for
this example, so we need to specify the atom-pc branch and get the
SRCREVs for atom-pc or the step that modifies the
linux-yocto_3.0.bbappend. So in
meta-yocto/recipes-kernel/linux/linux-yocto_3.0.bbappend, we find both
the KMACHINE branch we need, and the SRCREV on that branch we need for
edison. Since that doesn't specify the meta branch, but the base
recipe does, we can look at the SRCREV_meta there
(meta/recipes-kernel/linux/linux-yocto_3.0.bb) for the SRCREV of the
meta branch, which already matches what we're using, so no change
needed there.

Here's the resulting linux-yocto_3.0.bbappend:

***@elmorro:/usr/local/dev/yocto/bsp-test/poky/meta-intel$ cat meta-mymachine/recipes-kernel/linux/linux-yocto_3.0.bbappend

FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"

COMPATIBLE_MACHINE_mymachine = "mymachine"
KMACHINE_mymachine = "yocto/standard/common-pc/atom-pc"
KERNEL_FEATURES_append_mymachine += " cfg/smp.scc"

SRCREV_machine_pn-linux-yocto_mymachine ?= "1e18e44adbe79b846e382370eb29bc4b8cd5a1a0"
SRCREV_meta_pn-linux-yocto_mymachine ?= "d05450e4aef02c1b7137398ab3a9f8f96da74f52"

----

***@elmorro:/usr/local/dev/yocto/bsp-test/poky$ source oe-init-build-env
***@elmorro:/usr/local/dev/yocto/bsp-test/poky$ bitbake core-image-sato

NOTE: Tasks Summary: Attempted 4426 tasks of which 247 didn't need to be rerun and 0 failed.
***@elmorro:/usr/local/dev/yocto/bsp-test/poky/build


Tom
Post by James Abernathy
Just to clear up the basics, Prior to following Appendix A verbatim, I
did the following
1. install prerequisites from GS guide
2. git clone git://git.yoctoproject.org/poky
3. cd poky
4. git clone git://git.yoctoproject.org/meta-intel.git
I did not install the poky-extras. I assumed it only had to be
installed if you installed the kernel source for modification like in
Appendix b
Jim a
Hi,
Post by James Abernathy
I tried to duplicate the Yocto Project Decelopment Manual
Appendix A
Post by James Abernathy
build of a Crownbay NOEMGD image, no changes just dulicate
the
Post by James Abernathy
instructions. This is using the latest Yocto 1.1. I did
get a long
Post by James Abernathy
way down the line, but had a fatal error in the last 2
steps.
Post by James Abernathy
The only change I had to make was related to A.5.2.4. The
commit
Post by James Abernathy
string for the SRCREV_meta_pn was different on the
git.yoctoproject.org/cgit/cgi for the Meta commit so I used
what I
Post by James Abernathy
found online. The first section of 126 task completed
without error.
Post by James Abernathy
The next section of 4394 tasks failed on 4393. Not sure if
the error
Post by James Abernathy
is obvious, but I wanted to run it by someone. Console error
log
Hmm, not sure what's going on here - I'm sure this example was verified
several times, but just to make sure, what you're doing is going through
'Appendix A. BSP Development Example' verbatim and getting this?
The SRCREVs in either case look ok for this, so that shouldn't be the
problem...
But let me go over the steps myself and see what I come up with - will
let you know either way...
Tom
Started
Post by James Abernathy
ERROR: Function 'build_boot_bin' failed
(see /home/jim/poky/yocto-build/tmp/work/mymachine-poky-linux/core-image-sato-1.0-r0/temp/log.do_bootimg.31418 for further information)
Post by James Abernathy
ERROR: Logfile of failure stored
in: /home/jim/poky/yocto-build/tmp/work/mymachine-poky-linux/core-image-sato-1.0-r0/temp/log.do_bootimg.31418
Post by James Abernathy
| install: cannot stat
`/home/jim/poky/yocto-build/tmp/sysroots/mymachine/kernel/bzImage': No
Post by James Abernathy
such file or directory
| ERROR: Function 'build_boot_bin' failed
(see /home/jim/poky/yocto-build/tmp/work/mymachine-poky-linux/core-image-sato-1.0-r0/temp/log.do_bootimg.31418 for further information)
Failed
Post by James Abernathy
ERROR: Task 9
(/home/jim/poky/meta/recipes-sato/images/core-image-sato.bb,
do_bootimg) failed with exit code '1'
'/home/jim/poky/meta/recipes-sato/images/core-image-sato.bb'
Post by James Abernathy
failed
Robert P. J. Day
2011-11-02 12:19:03 UTC
Permalink
just to clarify any overlooked issues ...
... I captured the steps I used below, which should work in the same
way for you.
should one still change the NAME or DESCRIPTION comments in that new
mymachine.conf file to reflect "mymachine" as the dev-manual suggests,
or can one just leave them referring to crownbay? recall that the
current dev-manual claims that you "need" to make those changes. if
you don't, that claim should be softened.

also, there's no mention of editing "layer.conf" to reflect
"mymachine" as directed in dev-manual:

BBFILE_COLLECTIONS += "mymachine"

should that not be done? again, the current dev-manual states that
that change is "needed".
don't you also have to rename "crownbay-noemgd/" to "mymachine/"
under that recipes-graphics/ directory as well, as the dev-manual
directs? you don't mention that here. you also don't mention making
editing changes to recipes-core/tasks/task-core-tools.bbappend as
dev-manual suggests. not necessary?
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
COMPATIBLE_MACHINE_mymachine = "mymachine"
KMACHINE_mymachine = "yocto/standard/common-pc/atom-pc"
KERNEL_FEATURES_append_mymachine += " cfg/smp.scc"
SRCREV_machine_pn-linux-yocto_mymachine ?= "1e18e44adbe79b846e382370eb29bc4b8cd5a1a0"
SRCREV_meta_pn-linux-yocto_mymachine ?= "d05450e4aef02c1b7137398ab3a9f8f96da74f52"
ok, just took that verbatim.
NOTE: Tasks Summary: Attempted 4426 tasks of which 247 didn't need to be rerun and 0 failed.
other than sourcing from one directory level up and making the
appropriate changes in conf/local.conf to refer to "mymachine", no
difference here. just started the build ...

rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
Tom Zanussi
2011-11-02 14:18:39 UTC
Permalink
Post by Robert P. J. Day
just to clarify any overlooked issues ...
... I captured the steps I used below, which should work in the same
way for you.
should one still change the NAME or DESCRIPTION comments in that new
mymachine.conf file to reflect "mymachine" as the dev-manual suggests,
or can one just leave them referring to crownbay? recall that the
current dev-manual claims that you "need" to make those changes. if
you don't, that claim should be softened.
Right, not strictly needed, only for consistency, so the language should
be softened, I agree.
Post by Robert P. J. Day
also, there's no mention of editing "layer.conf" to reflect
BBFILE_COLLECTIONS += "mymachine"
should that not be done? again, the current dev-manual states that
that change is "needed".
That is needed, but the steps that required editing files aren't easily
captured in a transcript, so I didn't capture those, but they are still
required. I should have added a <do editing step xxx from the doc here>
to make that clear, though I did mention that other than the
kernel .bbappend, the steps I went through were pretty much as
described. Anyway, hopefully we can get the changes from this thread in
the doc and it will then all fit together.
Post by Robert P. J. Day
don't you also have to rename "crownbay-noemgd/" to "mymachine/"
under that recipes-graphics/ directory as well, as the dev-manual
directs? you don't mention that here. you also don't mention making
Right, I missed that step. It still builds, though there would be
problems with X at runtime due to this.
Post by Robert P. J. Day
editing changes to recipes-core/tasks/task-core-tools.bbappend as
dev-manual suggests. not necessary?
Yes, necessary, again, I didn't add the notes about editing.

Tom
Post by Robert P. J. Day
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
COMPATIBLE_MACHINE_mymachine = "mymachine"
KMACHINE_mymachine = "yocto/standard/common-pc/atom-pc"
KERNEL_FEATURES_append_mymachine += " cfg/smp.scc"
SRCREV_machine_pn-linux-yocto_mymachine ?= "1e18e44adbe79b846e382370eb29bc4b8cd5a1a0"
SRCREV_meta_pn-linux-yocto_mymachine ?= "d05450e4aef02c1b7137398ab3a9f8f96da74f52"
ok, just took that verbatim.
NOTE: Tasks Summary: Attempted 4426 tasks of which 247 didn't need to be rerun and 0 failed.
other than sourcing from one directory level up and making the
appropriate changes in conf/local.conf to refer to "mymachine", no
difference here. just started the build ...
rday
Robert P. J. Day
2011-11-02 14:35:49 UTC
Permalink
... all of tom's stuff snipped ...

ok, based on combining everything in the last several posts, my
build for core-image-sato for the new "mymachine" bsp just finished
successfully on my 64-bit ubuntu 11.10 system. happy, happy, joy,
joy. must write this all down somewhere. :-)

rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
Jim Abernathy
2011-11-02 14:24:27 UTC
Permalink
okay, what you mentioned as the steps below, I agree with, but a couple
I don't understand. first, in the linux-yocto_3.0.bbappend file, why is
the KMACHINE statement changed to common-pc/atom-pc? If I look st eh
section of the doc in A.5.2.4 talking about going to
cgit/cgit.cgi/linux-yocto-3.0 to get the latest commit strings, I see
that it agrees with the path in #2, but not sure why??

Second, I looked at your cat of the same file containing the SRCREV
commit strings and I don't see that they agree with the commits on the
website even just this morning. Can you explain that? Should I just use
the ones in your cat output or eventually the corrected Dev. Manual?

Jim A
Post by Tom Zanussi
Hi James,
I'm still not sure what happened in your case to cause this problem, but
I just went through the Appendix A example pretty much as described, and
got a good build out of it. There was one particular part of the
example that wasn't exactly clear and that could definitely cause some
build problems if you did it incorrectly (the section that makes changes
to linux-yocto_3.0.bbappend, which in the example has a custom branch in
the .bbappend file, but has the explanation using atom-pc).
I'll work with Scott to make sure that part gets cleaned up, along with
the other comments that should get pulled in, but in the meantime, I
captured the steps I used below, which should work in the same way for
you.
----
The Developer's Manual seems to want to base the BSP on atom-pc for
this example, so we need to specify the atom-pc branch and get the
SRCREVs for atom-pc or the step that modifies the
linux-yocto_3.0.bbappend. So in
meta-yocto/recipes-kernel/linux/linux-yocto_3.0.bbappend, we find both
the KMACHINE branch we need, and the SRCREV on that branch we need for
edison. Since that doesn't specify the meta branch, but the base
recipe does, we can look at the SRCREV_meta there
(meta/recipes-kernel/linux/linux-yocto_3.0.bb) for the SRCREV of the
meta branch, which already matches what we're using, so no change
needed there.
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
COMPATIBLE_MACHINE_mymachine = "mymachine"
KMACHINE_mymachine = "yocto/standard/common-pc/atom-pc"
KERNEL_FEATURES_append_mymachine += " cfg/smp.scc"
SRCREV_machine_pn-linux-yocto_mymachine ?= "1e18e44adbe79b846e382370eb29bc4b8cd5a1a0"
SRCREV_meta_pn-linux-yocto_mymachine ?= "d05450e4aef02c1b7137398ab3a9f8f96da74f52"
----
NOTE: Tasks Summary: Attempted 4426 tasks of which 247 didn't need to be rerun and 0 failed.
Tom
Post by James Abernathy
Just to clear up the basics, Prior to following Appendix A verbatim, I
did the following
1. install prerequisites from GS guide
2. git clone git://git.yoctoproject.org/poky
3. cd poky
4. git clone git://git.yoctoproject.org/meta-intel.git
I did not install the poky-extras. I assumed it only had to be
installed if you installed the kernel source for modification like in
Appendix b
Jim a
Hi,
Post by James Abernathy
I tried to duplicate the Yocto Project Decelopment Manual
Appendix A
Post by James Abernathy
build of a Crownbay NOEMGD image, no changes just dulicate
the
Post by James Abernathy
instructions. This is using the latest Yocto 1.1. I did
get a long
Post by James Abernathy
way down the line, but had a fatal error in the last 2
steps.
Post by James Abernathy
The only change I had to make was related to A.5.2.4. The
commit
Post by James Abernathy
string for the SRCREV_meta_pn was different on the
git.yoctoproject.org/cgit/cgi for the Meta commit so I used
what I
Post by James Abernathy
found online. The first section of 126 task completed
without error.
Post by James Abernathy
The next section of 4394 tasks failed on 4393. Not sure if
the error
Post by James Abernathy
is obvious, but I wanted to run it by someone. Console error
log
Hmm, not sure what's going on here - I'm sure this example was verified
several times, but just to make sure, what you're doing is
going through
'Appendix A. BSP Development Example' verbatim and getting this?
The SRCREVs in either case look ok for this, so that shouldn't be the
problem...
But let me go over the steps myself and see what I come up with - will
let you know either way...
Tom
Started
Post by James Abernathy
ERROR: Function 'build_boot_bin' failed
(see /home/jim/poky/yocto-build/tmp/work/mymachine-poky-linux/core-image-sato-1.0-r0/temp/log.do_bootimg.31418 for further information)
Post by James Abernathy
ERROR: Logfile of failure stored
in: /home/jim/poky/yocto-build/tmp/work/mymachine-poky-linux/core-image-sato-1.0-r0/temp/log.do_bootimg.31418
Post by James Abernathy
| install: cannot stat
`/home/jim/poky/yocto-build/tmp/sysroots/mymachine/kernel/bzImage': No
Post by James Abernathy
such file or directory
| ERROR: Function 'build_boot_bin' failed
(see /home/jim/poky/yocto-build/tmp/work/mymachine-poky-linux/core-image-sato-1.0-r0/temp/log.do_bootimg.31418 for further information)
Failed
Post by James Abernathy
ERROR: Task 9
(/home/jim/poky/meta/recipes-sato/images/core-image-sato.bb,
do_bootimg) failed with exit code '1'
'/home/jim/poky/meta/recipes-sato/images/core-image-sato.bb'
Post by James Abernathy
failed
Tom Zanussi
2011-11-02 14:41:52 UTC
Permalink
Post by Jim Abernathy
okay, what you mentioned as the steps below, I agree with, but a couple
I don't understand. first, in the linux-yocto_3.0.bbappend file, why is
the KMACHINE statement changed to common-pc/atom-pc? If I look st eh
section of the doc in A.5.2.4 talking about going to
cgit/cgit.cgi/linux-yocto-3.0 to get the latest commit strings, I see
that it agrees with the path in #2, but not sure why??
This is part of the confusion I mentioned about this section that needs
to be cleaned up. Basically, for this example, to keep things simple,
we want to use an already-existing branch in the repo. The branch that
was somewhat vaguely chosen for this example was the atom-pc branch. So
this should be the branch specified in the KMACHINE, which my
corrected .bbappend shows, rather than the "yocto/standard/mymachine" in
the example code.

The mention of cgit/cgit.cgi/linux-yocto-3.0 to get the latest commit
strings is correct assuming you're working from master. But this
example is working from edison, where there commits to use are
essentially set in stone and contained in the SRCREVs in the .bb
and .bbappends in the edison branch.

Again, this is part of the confusion in this section that needs cleaning
up.
Post by Jim Abernathy
Second, I looked at your cat of the same file containing the SRCREV
commit strings and I don't see that they agree with the commits on the
website even just this morning. Can you explain that? Should I just use
the ones in your cat output or eventually the corrected Dev. Manual?
I got these commits from the kernel .bb and .bbappends captured in the
edison branch, as mentioened above.

Tom
Post by Jim Abernathy
Jim A
Post by Tom Zanussi
Hi James,
I'm still not sure what happened in your case to cause this problem, but
I just went through the Appendix A example pretty much as described, and
got a good build out of it. There was one particular part of the
example that wasn't exactly clear and that could definitely cause some
build problems if you did it incorrectly (the section that makes changes
to linux-yocto_3.0.bbappend, which in the example has a custom branch in
the .bbappend file, but has the explanation using atom-pc).
I'll work with Scott to make sure that part gets cleaned up, along with
the other comments that should get pulled in, but in the meantime, I
captured the steps I used below, which should work in the same way for
you.
----
The Developer's Manual seems to want to base the BSP on atom-pc for
this example, so we need to specify the atom-pc branch and get the
SRCREVs for atom-pc or the step that modifies the
linux-yocto_3.0.bbappend. So in
meta-yocto/recipes-kernel/linux/linux-yocto_3.0.bbappend, we find both
the KMACHINE branch we need, and the SRCREV on that branch we need for
edison. Since that doesn't specify the meta branch, but the base
recipe does, we can look at the SRCREV_meta there
(meta/recipes-kernel/linux/linux-yocto_3.0.bb) for the SRCREV of the
meta branch, which already matches what we're using, so no change
needed there.
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
COMPATIBLE_MACHINE_mymachine = "mymachine"
KMACHINE_mymachine = "yocto/standard/common-pc/atom-pc"
KERNEL_FEATURES_append_mymachine += " cfg/smp.scc"
SRCREV_machine_pn-linux-yocto_mymachine ?= "1e18e44adbe79b846e382370eb29bc4b8cd5a1a0"
SRCREV_meta_pn-linux-yocto_mymachine ?= "d05450e4aef02c1b7137398ab3a9f8f96da74f52"
----
NOTE: Tasks Summary: Attempted 4426 tasks of which 247 didn't need to be rerun and 0 failed.
Tom
Post by James Abernathy
Just to clear up the basics, Prior to following Appendix A verbatim, I
did the following
1. install prerequisites from GS guide
2. git clone git://git.yoctoproject.org/poky
3. cd poky
4. git clone git://git.yoctoproject.org/meta-intel.git
I did not install the poky-extras. I assumed it only had to be
installed if you installed the kernel source for modification like in
Appendix b
Jim a
Hi,
Post by James Abernathy
I tried to duplicate the Yocto Project Decelopment Manual
Appendix A
Post by James Abernathy
build of a Crownbay NOEMGD image, no changes just dulicate
the
Post by James Abernathy
instructions. This is using the latest Yocto 1.1. I did
get a long
Post by James Abernathy
way down the line, but had a fatal error in the last 2
steps.
Post by James Abernathy
The only change I had to make was related to A.5.2.4. The
commit
Post by James Abernathy
string for the SRCREV_meta_pn was different on the
git.yoctoproject.org/cgit/cgi for the Meta commit so I used
what I
Post by James Abernathy
found online. The first section of 126 task completed
without error.
Post by James Abernathy
The next section of 4394 tasks failed on 4393. Not sure if
the error
Post by James Abernathy
is obvious, but I wanted to run it by someone. Console error
log
Hmm, not sure what's going on here - I'm sure this example was
verified
several times, but just to make sure, what you're doing is
going through
'Appendix A. BSP Development Example' verbatim and getting this?
The SRCREVs in either case look ok for this, so that shouldn't
be the
problem...
But let me go over the steps myself and see what I come up
with - will
let you know either way...
Tom
Started
Post by James Abernathy
ERROR: Function 'build_boot_bin' failed
(see /home/jim/poky/yocto-build/tmp/work/mymachine-poky-linux/core-image-sato-1.0-r0/temp/log.do_bootimg.31418 for further information)
Post by James Abernathy
ERROR: Logfile of failure stored
in: /home/jim/poky/yocto-build/tmp/work/mymachine-poky-linux/core-image-sato-1.0-r0/temp/log.do_bootimg.31418
Post by James Abernathy
| install: cannot stat
`/home/jim/poky/yocto-build/tmp/sysroots/mymachine/kernel/bzImage': No
Post by James Abernathy
such file or directory
| ERROR: Function 'build_boot_bin' failed
(see /home/jim/poky/yocto-build/tmp/work/mymachine-poky-linux/core-image-sato-1.0-r0/temp/log.do_bootimg.31418 for further information)
Failed
Post by James Abernathy
ERROR: Task 9
(/home/jim/poky/meta/recipes-sato/images/core-image-sato.bb,
do_bootimg) failed with exit code '1'
'/home/jim/poky/meta/recipes-sato/images/core-image-sato.bb'
Post by James Abernathy
failed
Jim Abernathy
2011-11-02 15:07:47 UTC
Permalink
Post by Tom Zanussi
Post by Jim Abernathy
Second, I looked at your cat of the same file containing the SRCREV
commit strings and I don't see that they agree with the commits on the
website even just this morning. Can you explain that? Should I just use
the ones in your cat output or eventually the corrected Dev. Manual?
I got these commits from the kernel .bb and .bbappends captured in the
edison branch, as mentioened above.
That's a lot clearer now. So does this mean that If I'm working with
edison branch, should I have to change the commits strings at all???

Because the commit strings from your cat'ing of the your file don't
agree with what is in my clone of the edison branch for poky or
meta-intel. Or am I missing something else (likely).

Jim A
Tom Zanussi
2011-11-02 15:34:33 UTC
Permalink
Post by Jim Abernathy
Post by Tom Zanussi
Post by Jim Abernathy
Second, I looked at your cat of the same file containing the SRCREV
commit strings and I don't see that they agree with the commits on the
website even just this morning. Can you explain that? Should I just use
the ones in your cat output or eventually the corrected Dev. Manual?
I got these commits from the kernel .bb and .bbappends captured in the
edison branch, as mentioened above.
That's a lot clearer now. So does this mean that If I'm working with
edison branch, should I have to change the commits strings at all???
The commits in the doc should work - the SRCREV_machine is the last
commit on the edison branch for yocto/standard/common-pc/atom-pc and the
SRCREV_meta is also valid in edison, though in between the time the doc
was written and the time meta-intel was released for edison, the meta
SRCREV was bumped up to a later commit, which is the one I used in my
'cat'ed file. Either one should be fine. So no, you can directly use
the SRCREVS in the manual and don't have to change those at all.
Post by Jim Abernathy
Because the commit strings from your cat'ing of the your file don't
agree with what is in my clone of the edison branch for poky or
meta-intel. Or am I missing something else (likely).
Those commit strings identify commits in the linux-yocto_3.0 repo
(http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.0/). The
specific commits used for edison are captured in the linux-yocto_3.0 .bb
and .bbappend files mentioned previously.

Tom
Post by Jim Abernathy
Jim A
Jim Abernathy
2011-11-02 19:18:18 UTC
Permalink
Well, I finally got a "successful" build without erros of the Appendix A
example for Crownbay, but the image created was only 216MB in size and
kernel panic'ed because it couldn't find a valid root file system.

I'm going to try again from scratch and see if I missed anything. If
that fails, I'll report out.

Jim A
Tom Zanussi
2011-11-02 19:36:36 UTC
Permalink
Post by Jim Abernathy
Well, I finally got a "successful" build without erros of the Appendix A
example for Crownbay, but the image created was only 216MB in size and
kernel panic'ed because it couldn't find a valid root file system.
That size doesn't sound right. Here's mine:

-rw-r--r-- 1 trz trz 358715392 2011-11-01 19:11 core-image-sato-mymachine-20111101223904.hddimg

And what kind of machine are you booting it on?

Tom
Post by Jim Abernathy
I'm going to try again from scratch and see if I missed anything. If
that fails, I'll report out.
Jim A
Jim Abernathy
2011-11-02 20:07:25 UTC
Permalink
Post by Tom Zanussi
And what kind of machine are you booting it on?
Tom
I'm building on Core i5 desktop with Ubuntu 10.10. One of the odd
things I've noticed during the build is it takes the usual long time
(couple of hours) to build. However when it get to task ~4000, it jumps
quickly to 43xx close to the end. Not sure if it's missing something
critical and I've not set some parameter about the Root file system
somewhere.

Jim
Tom Zanussi
2011-11-02 20:18:29 UTC
Permalink
Post by Jim Abernathy
Post by Tom Zanussi
And what kind of machine are you booting it on?
Tom
I'm building on Core i5 desktop with Ubuntu 10.10. One of the odd
things I've noticed during the build is it takes the usual long time
(couple of hours) to build. However when it get to task ~4000, it jumps
Yeah, that's not out of line with expectations. You are using
BB_NUMBER_THREADS and PARALLEL make in your local.conf, I assume.
Post by Jim Abernathy
quickly to 43xx close to the end. Not sure if it's missing something
critical and I've not set some parameter about the Root file system
somewhere.
I wouldn't pay too much attention to the task numbers themselves - some
tasks take very little time and finish in quick progression. And
there's nothing specific about a root filesystem setting in the appendix
instructions, we're just copying existing working settings, but there is
something wrong with your build nonetheless.

I'm planning on submitting a patch to the appendix as soon as I can
today or tomorrow morning, which I'll work through and verify, so you
shouldn't have to do any guesswork and shouldn't run into any of these
kinds of problems...

Tom
Post by Jim Abernathy
Jim
Jim Abernathy
2011-11-02 22:05:05 UTC
Permalink
I'm noticing fetcher failures while my bitbake is working. They are
listed as warning. Do I ignore these??

WARNING: Fetcher failure for URL: 'None'. Fetch command export
HOME="/home/jim"; export SSH_AGENT_PID="1500"; export
SSH_AUTH_SOCK="/tmp/keyring-Zcbzax/ssh"; export
GIT_CONFIG="/home/jim/bsp-test/poky/build/tmp/sysroots/i686-linux/usr/etc/gitconfig"; export PATH="/home/jim/bsp-test/poky/build/tmp/sysroots/i686-linux/usr/bin/core2-poky-linux:/home/jim/bsp-test/poky/build/tmp/sysroots/mymachine/usr/bin/crossscripts:/home/jim/bsp-test/poky/build/tmp/sysroots/i686-linux/usr/sbin:/home/jim/bsp-test/poky/build/tmp/sysroots/i686-linux/usr/bin:/home/jim/bsp-test/poky/build/tmp/sysroots/i686-linux/sbin:/home/jim/bsp-test/poky/build/tmp/sysroots/i686-linux//bin:/home/jim/bsp-test/poky/scripts:/home/jim/bsp-test/poky/bitbake/bin/:/home/jim/bsp-test/poky/scripts:/home/jim/bsp-test/poky/bitbake/bin/:/home/jim/bsp-test/poky/scripts:/home/jim/bsp-test/poky/bitbake/bin/:/home/jim/bsp-test/poky/scripts:/home/jim/bsp-test/poky/bitbake/bin/:/home/jim/poky/scripts:/home/
jim/poky/bitbake/bin/:/home/jim/poky/scripts:/home/jim/poky/bitbake/bin/:/home/jim/CodeSourcery/Sourcery_G++_Lite/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:
/home/jim/bsp-test/poky/scripts"; /usr/bin/env wget -t 5 -q --passive-ftp --no-check-certificate -P /home/jim/bsp-test/poky/build/downloads 'https://fedorahosted.org/releases/l/i/liberation-fonts/liberation-fonts-1.04.tar.gz' failed with signal 4, output:
James Abernathy
2011-11-03 19:32:14 UTC
Permalink
I had some success, so I thought I'd report that out:

Following a combination of the Yocto Project Development Manual and Tom's
notes below, I got a successful
build and the image booted from a USB flash drive on a Crownbay Development
platform, without EMGD GFX driver.
The only change I needed to make it bootable from Tom's instructions was to
make KMACHINE_mymachine = "yocto/standard/crownbay" and
put in the correct SRCREV commit strings for the crownbay using the
"howto" instructions in Appendix A.5.2.4 6th paragraph.

Now on to making the EMGD image work.

Jim A
Post by Tom Zanussi
Hi James,
I'm still not sure what happened in your case to cause this problem, but
I just went through the Appendix A example pretty much as described, and
got a good build out of it. There was one particular part of the
example that wasn't exactly clear and that could definitely cause some
build problems if you did it incorrectly (the section that makes changes
to linux-yocto_3.0.bbappend, which in the example has a custom branch in
the .bbappend file, but has the explanation using atom-pc).
I'll work with Scott to make sure that part gets cleaned up, along with
the other comments that should get pulled in, but in the meantime, I
captured the steps I used below, which should work in the same way for
you.
git.yoctoproject.org/poky
git.yoctoproject.org/meta-intel.git
-b edison origin/edison
meta-crownbay/ meta-mymachine
meta-mymachine/conf/machine/crownbay.conf
meta-mymachine/conf/machine/crownbay-noemgd.conf
meta-mymachine/conf/machine/mymachine.conf
meta-mymachine/recipes-bsp/formfactor/formfactor/crownbay/
meta-mymachine/recipes-bsp/formfactor/formfactor/crownbay-noemgd
meta-mymachine/recipes-bsp/formfactor/formfactor/mymachine
meta-mymachine/recipes-graphics/xorg-xserver/xserver-xf86-config/crownbay
----
The Developer's Manual seems to want to base the BSP on atom-pc for
this example, so we need to specify the atom-pc branch and get the
SRCREVs for atom-pc or the step that modifies the
linux-yocto_3.0.bbappend. So in
meta-yocto/recipes-kernel/linux/linux-yocto_3.0.bbappend, we find both
the KMACHINE branch we need, and the SRCREV on that branch we need for
edison. Since that doesn't specify the meta branch, but the base
recipe does, we can look at the SRCREV_meta there
(meta/recipes-kernel/linux/linux-yocto_3.0.bb) for the SRCREV of the
meta branch, which already matches what we're using, so no change
needed there.
meta-mymachine/recipes-kernel/linux/linux-yocto_3.0.bbappend
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
COMPATIBLE_MACHINE_mymachine = "mymachine"
KMACHINE_mymachine = "yocto/standard/common-pc/atom-pc"
KERNEL_FEATURES_append_mymachine += " cfg/smp.scc"
SRCREV_machine_pn-linux-yocto_mymachine ?=
"1e18e44adbe79b846e382370eb29bc4b8cd5a1a0"
SRCREV_meta_pn-linux-yocto_mymachine ?=
"d05450e4aef02c1b7137398ab3a9f8f96da74f52"
----
NOTE: Tasks Summary: Attempted 4426 tasks of which 247 didn't need to be
rerun and 0 failed.
Tom
Post by James Abernathy
Just to clear up the basics, Prior to following Appendix A verbatim, I
did the following
1. install prerequisites from GS guide
2. git clone git://git.yoctoproject.org/poky
3. cd poky
4. git clone git://git.yoctoproject.org/meta-intel.git
I did not install the poky-extras. I assumed it only had to be
installed if you installed the kernel source for modification like in
Appendix b
Jim a
Hi,
Post by James Abernathy
I tried to duplicate the Yocto Project Decelopment Manual
Appendix A
Post by James Abernathy
build of a Crownbay NOEMGD image, no changes just dulicate
the
Post by James Abernathy
instructions. This is using the latest Yocto 1.1. I did
get a long
Post by James Abernathy
way down the line, but had a fatal error in the last 2
steps.
Post by James Abernathy
The only change I had to make was related to A.5.2.4. The
commit
Post by James Abernathy
string for the SRCREV_meta_pn was different on the
git.yoctoproject.org/cgit/cgi for the Meta commit so I used
what I
Post by James Abernathy
found online. The first section of 126 task completed
without error.
Post by James Abernathy
The next section of 4394 tasks failed on 4393. Not sure if
the error
Post by James Abernathy
is obvious, but I wanted to run it by someone. Console error
log
Hmm, not sure what's going on here - I'm sure this example was verified
several times, but just to make sure, what you're doing is
going through
'Appendix A. BSP Development Example' verbatim and getting this?
The SRCREVs in either case look ok for this, so that shouldn't be the
problem...
But let me go over the steps myself and see what I come up with - will
let you know either way...
Tom
Started
Post by James Abernathy
ERROR: Function 'build_boot_bin' failed
(see
/home/jim/poky/yocto-build/tmp/work/mymachine-poky-linux/core-image-sato-1.0-r0/temp/log.do_bootimg.31418
for further information)
Post by James Abernathy
Post by James Abernathy
ERROR: Logfile of failure stored
/home/jim/poky/yocto-build/tmp/work/mymachine-poky-linux/core-image-sato-1.0-r0/temp/log.do_bootimg.31418
Post by James Abernathy
Post by James Abernathy
| install: cannot stat
`/home/jim/poky/yocto-build/tmp/sysroots/mymachine/kernel/bzImage': No
Post by James Abernathy
Post by James Abernathy
such file or directory
| ERROR: Function 'build_boot_bin' failed
(see
/home/jim/poky/yocto-build/tmp/work/mymachine-poky-linux/core-image-sato-1.0-r0/temp/log.do_bootimg.31418
for further information)
Post by James Abernathy
Failed
Post by James Abernathy
ERROR: Task 9
(/home/jim/poky/meta/recipes-sato/images/core-image-sato.bb,
do_bootimg) failed with exit code '1'
'/home/jim/poky/meta/recipes-sato/images/core-image-sato.bb'
Post by James Abernathy
failed
Robert P. J. Day
2011-11-01 21:37:28 UTC
Permalink
Post by Tom Zanussi
Hi,
Post by James Abernathy
I tried to duplicate the Yocto Project Decelopment Manual Appendix A
build of a Crownbay NOEMGD image, no changes just dulicate the
instructions. This is using the latest Yocto 1.1. I did get a long
way down the line, but had a fatal error in the last 2 steps.
The only change I had to make was related to A.5.2.4. The commit
string for the SRCREV_meta_pn was different on the
git.yoctoproject.org/cgit/cgi for the Meta commit so I used what I
found online. The first section of 126 task completed without error.
The next section of 4394 tasks failed on 4393. Not sure if the error
is obvious, but I wanted to run it by someone. Console error log
Hmm, not sure what's going on here - I'm sure this example was
verified several times, but just to make sure, what you're doing is
going through 'Appendix A. BSP Development Example' verbatim and
getting this?
ironically, i'm working on this very example and something in the
dev manual doesn't look right. section A.5.2.1:

These commands take care of the recipes-bsp recipes:

$ rm -rf meta-mymachine/recipes-graphics/xorg-xserver/*emgd*
... snip ...

why is that command referring to the recipes-graphics directory when
this section is supposed to be adjusting recipes-bsp?

or have i screwed something up?

rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
Tom Zanussi
2011-11-01 21:46:08 UTC
Permalink
Post by Robert P. J. Day
Post by Tom Zanussi
Hi,
Post by James Abernathy
I tried to duplicate the Yocto Project Decelopment Manual Appendix A
build of a Crownbay NOEMGD image, no changes just dulicate the
instructions. This is using the latest Yocto 1.1. I did get a long
way down the line, but had a fatal error in the last 2 steps.
The only change I had to make was related to A.5.2.4. The commit
string for the SRCREV_meta_pn was different on the
git.yoctoproject.org/cgit/cgi for the Meta commit so I used what I
found online. The first section of 126 task completed without error.
The next section of 4394 tasks failed on 4393. Not sure if the error
is obvious, but I wanted to run it by someone. Console error log
Hmm, not sure what's going on here - I'm sure this example was
verified several times, but just to make sure, what you're doing is
going through 'Appendix A. BSP Development Example' verbatim and
getting this?
ironically, i'm working on this very example and something in the
$ rm -rf meta-mymachine/recipes-graphics/xorg-xserver/*emgd*
... snip ...
why is that command referring to the recipes-graphics directory when
this section is supposed to be adjusting recipes-bsp?
or have i screwed something up?
You're right, that line shouldn't be there (it should be removed from
the instructions). The emgd recipes were moved out of meta-crownbay and
into meta-intel/common, so this step is no longer needed.

Tom
Post by Robert P. J. Day
rday
Tom Zanussi
2011-11-01 21:54:49 UTC
Permalink
Post by Tom Zanussi
Post by Robert P. J. Day
Post by Tom Zanussi
Hi,
Post by James Abernathy
I tried to duplicate the Yocto Project Decelopment Manual Appendix A
build of a Crownbay NOEMGD image, no changes just dulicate the
instructions. This is using the latest Yocto 1.1. I did get a long
way down the line, but had a fatal error in the last 2 steps.
The only change I had to make was related to A.5.2.4. The commit
string for the SRCREV_meta_pn was different on the
git.yoctoproject.org/cgit/cgi for the Meta commit so I used what I
found online. The first section of 126 task completed without error.
The next section of 4394 tasks failed on 4393. Not sure if the error
is obvious, but I wanted to run it by someone. Console error log
Hmm, not sure what's going on here - I'm sure this example was
verified several times, but just to make sure, what you're doing is
going through 'Appendix A. BSP Development Example' verbatim and
getting this?
ironically, i'm working on this very example and something in the
$ rm -rf meta-mymachine/recipes-graphics/xorg-xserver/*emgd*
... snip ...
why is that command referring to the recipes-graphics directory when
this section is supposed to be adjusting recipes-bsp?
or have i screwed something up?
You're right, that line shouldn't be there (it should be removed from
the instructions). The emgd recipes were moved out of meta-crownbay and
into meta-intel/common, so this step is no longer needed.
Probably what was meant was this instead:

rm -rf meta-mymachine/recipes-bsp/formfactor/formfactor/crownbay/

And of course the first line in section A.5.2.2. doesn't apply and
should be removed.

rm -rf meta-mymachine/recipes-graphics/xorg-xserver/xserver-xf86-emgd*

Tom
Post by Tom Zanussi
Tom
Post by Robert P. J. Day
rday
_______________________________________________
yocto mailing list
https://lists.yoctoproject.org/listinfo/yocto
Robert P. J. Day
2011-11-01 22:47:48 UTC
Permalink
some questions/observations as i'm getting close to the end of this
appendix (some of which you've already seen and addressed), all done
on my 64-bit ubuntu 11.10 system:

* section A.3: rather than force the reader to follow a link or go
to an earlier section, why not just supply the command to check out
meta-intel/?

$ git clone http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel

* section A.5.1: is it actually *necessary* to delete the
crownbay.conf file, and to change the comments in the mymachine.conf
file? admittedly, it's nice to keep things consistent, but if the
text claims that something is "needed", then it really should be
required.

* section A.5.2.1: as we've noted, that first command can be tossed.
in addition, should one remove the "crownbay" directory from that
location? since "crownbay" content is being removed from other
locations, it would be nice to be consistent.

* section A.5.2.2: delete first command

* section A.5.2.4: the "SRCREV_meta" values listed in the appendix
don't match what's in the actual file. so what are the correct
values?

... back to work ...

rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
Tom Zanussi
2011-11-01 23:16:36 UTC
Permalink
Post by Robert P. J. Day
some questions/observations as i'm getting close to the end of this
appendix (some of which you've already seen and addressed), all done
* section A.3: rather than force the reader to follow a link or go
to an earlier section, why not just supply the command to check out
meta-intel/?
$ git clone http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel
Makes sense to me. Also, the same comment would apply to the main poky
repo as well.
Post by Robert P. J. Day
* section A.5.1: is it actually *necessary* to delete the
crownbay.conf file, and to change the comments in the mymachine.conf
file? admittedly, it's nice to keep things consistent, but if the
text claims that something is "needed", then it really should be
required.
No, not strictly necessary, but assuming you're using these instructions
to create a new BSP, definitely desirable.
Post by Robert P. J. Day
* section A.5.2.1: as we've noted, that first command can be tossed.
in addition, should one remove the "crownbay" directory from that
location? since "crownbay" content is being removed from other
locations, it would be nice to be consistent.
* section A.5.2.2: delete first command
I think that's right.
Post by Robert P. J. Day
* section A.5.2.4: the "SRCREV_meta" values listed in the appendix
don't match what's in the actual file. so what are the correct
values?
Well, this example seems to assume you want to base it on the atom-pc
branch, so I guess we should use the value for that branch in meta-yocto
(meta-yocto/recipes-kernel/linux/linux-yocto_3.0.bbappend). The meta
branch SRCREV should be inherited from the main recipe
(meta/recipes-kernel/linux/linux-yocto_3.0.bb) which looks like it
matches the current value and doesn't need to be changed.

Or at least that's what I'm building now. I'll post the full transcript
assuming I get a good build out of it...

Tom
Post by Robert P. J. Day
... back to work ...
rday
Robert P. J. Day
2011-11-01 23:27:47 UTC
Permalink
On Tue, 1 Nov 2011, Tom Zanussi wrote:

... snip ...
Post by Tom Zanussi
Or at least that's what I'm building now. I'll post the full transcript
assuming I get a good build out of it...
i'm also into task 301 of 4426 of a build on my wicked cool,
quad-core ASUS laptop. i don't think this is going to take long.
more later ...

rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
Robert P. J. Day
2011-11-01 21:56:03 UTC
Permalink
... snip ...
Post by Tom Zanussi
Post by Robert P. J. Day
Post by Tom Zanussi
Hmm, not sure what's going on here - I'm sure this example was
verified several times, but just to make sure, what you're doing is
going through 'Appendix A. BSP Development Example' verbatim and
getting this?
ironically, i'm working on this very example and something in the
$ rm -rf meta-mymachine/recipes-graphics/xorg-xserver/*emgd*
... snip ...
why is that command referring to the recipes-graphics directory when
this section is supposed to be adjusting recipes-bsp?
or have i screwed something up?
You're right, that line shouldn't be there (it should be removed
from the instructions). The emgd recipes were moved out of
meta-crownbay and into meta-intel/common, so this step is no longer
needed.
let me finish following this through and i'll make notes on anything
else that looks odd and report back.

rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
Loading...