* Errors attempting to build AT91SAM9x5 BSP
@ 2012-11-09 18:27 Bryan Evenson
2012-11-13 16:26 ` Bryan Evenson
0 siblings, 1 reply; 8+ messages in thread
From: Bryan Evenson @ 2012-11-09 18:27 UTC (permalink / raw)
To: poky
All,
I am using an Atmel AT91SAM9G25 board and have been using the OpenEmbedded Classic development tree (2011.03-maintenance branch) to build images for my board. This setup is on Linux kernel 2.6.39 and uses a special patch from Atmel to add SAM9x5 support. There are some kernel fixes starting at kernel 3.2 that are applicable to my setup that I would like to incorporate into my image. After reading the Yocto Project documentation, I thought the best approach to take would be to use the Yocto Project tools to build a BSP for my AT91SAM9G25 board. So far I have been unsuccessful and I am looking for help.
What I've done so far:
1. Followed the instructions in Section 2.2 of the Development Manual to obtain the latest Yocto project release, Yocto Project kernel and poky extras from Git. Associated commit hashes are:
poky: e421e95de0ce430cc2c6db9b0712a66ab96288a1 (on branch master)
linux-yocto-3.4-git: 7eb5fbf903d9db90c3cf371b65e1f2a68d5676d7 (on branch master)
poky-extras: 33714938c2b246e4894225b3170cb8972a389618 (on branch master)
Build configuration as announced by Bitbake:
Build Configuration:
BB_VERSION = "1.16.0"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "qemuarm"
DISTRO = "poky"
DISTRO_VERSION = "1.3+snapshot-20121109"
TUNE_FEATURES = "armv5 dsp thumb arm926ejs"
TARGET_FPU = "soft"
meta
meta-yocto
meta-yocto-bsp = "master:e421e95de0ce430cc2c6db9b0712a66ab96288a1"
2. Modified the local.conf file for an arm setup in hopes of building a qemuarm image first with a modified kernel.
3. bitbake -c menuconfig virtual/kernel, and then modified the kernel configuration to fit my needs for a SAM9G25.
4. bitbake virtual/kernel
5. bitbake core-image-sato, which then fails. It is failing on compiling the util-linux package with the following log from log.do_compile:
DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common']
DEBUG: Executing shell function do_compile
NOTE: make -j 2 ARCH=arm CPU= CPUOPT= OPT= -O2 -pipe -g -feliminate-unused-debug-types
make all-recursive
make[1]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2'
Making all in include
make[2]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/include'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/include'
Making all in disk-utils
make[2]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/disk-utils'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/disk-utils'
Making all in fdisk
make[2]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/fdisk'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/fdisk'
Making all in getopt
make[2]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/getopt'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/getopt'
Making all in lib
make[2]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/lib'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/lib'
Making all in libuuid
make[2]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libuuid'
Making all in src
make[3]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libuuid/src'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libuuid/src'
Making all in man
make[3]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libuuid/man'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libuuid/man'
make[3]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libuuid'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libuuid'
make[2]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libuuid'
Making all in libblkid
make[2]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libblkid'
Making all in src
make[3]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libblkid/src'
Making all in superblocks
make[4]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libblkid/src/superblocks'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libblkid/src/superblocks'
Making all in topology
make[4]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libblkid/src/topology'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libblkid/src/topology'
Making all in partitions
make[4]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libblkid/src/partitions'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libblkid/src/partitions'
Making all in .
make[4]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libblkid/src'
make[4]: Nothing to be done for `all-am'.
make[4]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libblkid/src'
make[3]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libblkid/src'
Making all in samples
make[3]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libblkid/samples'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libblkid/samples'
make[3]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libblkid'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libblkid'
make[2]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libblkid'
Making all in libmount
make[2]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libmount'
Making all in src
make[3]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libmount/src'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libmount/src'
make[3]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libmount'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libmount'
make[2]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libmount'
Making all in man/ru
make[2]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/man/ru'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/man/ru'
Making all in login-utils
make[2]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/login-utils'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/login-utils'
Making all in misc-utils
make[2]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/misc-utils'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/misc-utils'
Making all in po
make[2]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/po'
make[2]: *** No rule to make target `all'. Stop.
make[2]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/po'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2'
make: *** [all] Error 2
ERROR: oe_runmake failed
ERROR: Function failed: do_compile (see /media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/temp/log.do_compile.31925 for further information)
6. I thought there might be e piece in the toolchain that was missing, so I did a "bitbake meta-toolchain", which resulted in the following error during the compilation of the nativesdk-gdbm package:
DEBUG: SITE files ['endian-little', 'bit-32', 'ix86-common', 'common-linux', 'common-glibc', 'i686-linux', 'common']
DEBUG: Executing shell function do_compile
NOTE: make -j 2
make all-recursive
make[1]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/i686-nativesdk-pokysdk-linux/nativesdk-gdbm-1.10-r3/gdbm-1.10'
Making all in po
make[2]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/i686-nativesdk-pokysdk-linux/nativesdk-gdbm-1.10-r3/gdbm-1.10/po'
make[2]: *** No rule to make target `all'. Stop.
make[2]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/i686-nativesdk-pokysdk-linux/nativesdk-gdbm-1.10-r3/gdbm-1.10/po'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/i686-nativesdk-pokysdk-linux/nativesdk-gdbm-1.10-r3/gdbm-1.10'
make: *** [all] Error 2
ERROR: oe_runmake failed
ERROR: Function failed: do_compile (see /media/sda3/yocto/poky-build/tmp/work/i686-nativesdk-pokysdk-linux/nativesdk-gdbm-1.10-r3/temp/log.do_compile.26132 for further information)
At this point I'm not sure why I'm seeing these errors and what is going wrong. I'd welcome any suggestions that would help me get the build to complete.
Thanks,
Bryan Evenson
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Errors attempting to build AT91SAM9x5 BSP
2012-11-09 18:27 Errors attempting to build AT91SAM9x5 BSP Bryan Evenson
@ 2012-11-13 16:26 ` Bryan Evenson
2012-11-13 17:10 ` Paul Eggleton
0 siblings, 1 reply; 8+ messages in thread
From: Bryan Evenson @ 2012-11-13 16:26 UTC (permalink / raw)
To: poky
All,
I decided to start over with the stable danny tarball instead of using the Git repository. I've been able to build a core-image-minimal QEMU image and run it in QEMU. After that I created my new BSP using the yocto-bsp script and added my new BSP to the build/conf/bblayers.conf file as directed in the BSP Guide. However, now whenever I try to use bitbake for anything I get the error message "NOTE: Your conf/bblayers.conf has been automatically updated. Please re-run bitbake." I've tried incrementing the LCONF_VERSION variable in conf/bblayers.conf and incrementing the CONF_VERSION in conf/local.conf. I've also tried issuing "bitbake -f -c clean core-image-minimal" and I get the same error. The only way I've been able to use bitbake again is to remove the line for my new BSP from the BBLAYERS variable in conf/bblayers.conf. What am I doing wrong?
Thanks,
Bryan
-----Original Message-----
From: poky-bounces@yoctoproject.org [mailto:poky-bounces@yoctoproject.org] On Behalf Of Bryan Evenson
Sent: Friday, November 09, 2012 1:28 PM
To: poky@yoctoproject.org
Subject: [poky] Errors attempting to build AT91SAM9x5 BSP
All,
I am using an Atmel AT91SAM9G25 board and have been using the OpenEmbedded Classic development tree (2011.03-maintenance branch) to build images for my board. This setup is on Linux kernel 2.6.39 and uses a special patch from Atmel to add SAM9x5 support. There are some kernel fixes starting at kernel 3.2 that are applicable to my setup that I would like to incorporate into my image. After reading the Yocto Project documentation, I thought the best approach to take would be to use the Yocto Project tools to build a BSP for my AT91SAM9G25 board. So far I have been unsuccessful and I am looking for help.
What I've done so far:
1. Followed the instructions in Section 2.2 of the Development Manual to obtain the latest Yocto project release, Yocto Project kernel and poky extras from Git. Associated commit hashes are:
poky: e421e95de0ce430cc2c6db9b0712a66ab96288a1 (on branch master)
linux-yocto-3.4-git: 7eb5fbf903d9db90c3cf371b65e1f2a68d5676d7 (on branch master)
poky-extras: 33714938c2b246e4894225b3170cb8972a389618 (on branch master)
Build configuration as announced by Bitbake:
Build Configuration:
BB_VERSION = "1.16.0"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "qemuarm"
DISTRO = "poky"
DISTRO_VERSION = "1.3+snapshot-20121109"
TUNE_FEATURES = "armv5 dsp thumb arm926ejs"
TARGET_FPU = "soft"
meta
meta-yocto
meta-yocto-bsp = "master:e421e95de0ce430cc2c6db9b0712a66ab96288a1"
2. Modified the local.conf file for an arm setup in hopes of building a qemuarm image first with a modified kernel.
3. bitbake -c menuconfig virtual/kernel, and then modified the kernel configuration to fit my needs for a SAM9G25.
4. bitbake virtual/kernel
5. bitbake core-image-sato, which then fails. It is failing on compiling the util-linux package with the following log from log.do_compile:
DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common']
DEBUG: Executing shell function do_compile
NOTE: make -j 2 ARCH=arm CPU= CPUOPT= OPT= -O2 -pipe -g -feliminate-unused-debug-types make all-recursive
make[1]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2'
Making all in include
make[2]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/include'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/include'
Making all in disk-utils
make[2]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/disk-utils'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/disk-utils'
Making all in fdisk
make[2]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/fdisk'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/fdisk'
Making all in getopt
make[2]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/getopt'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/getopt'
Making all in lib
make[2]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/lib'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/lib'
Making all in libuuid
make[2]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libuuid'
Making all in src
make[3]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libuuid/src'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libuuid/src'
Making all in man
make[3]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libuuid/man'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libuuid/man'
make[3]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libuuid'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libuuid'
make[2]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libuuid'
Making all in libblkid
make[2]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libblkid'
Making all in src
make[3]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libblkid/src'
Making all in superblocks
make[4]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libblkid/src/superblocks'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libblkid/src/superblocks'
Making all in topology
make[4]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libblkid/src/topology'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libblkid/src/topology'
Making all in partitions
make[4]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libblkid/src/partitions'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libblkid/src/partitions'
Making all in .
make[4]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libblkid/src'
make[4]: Nothing to be done for `all-am'.
make[4]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libblkid/src'
make[3]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libblkid/src'
Making all in samples
make[3]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libblkid/samples'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libblkid/samples'
make[3]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libblkid'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libblkid'
make[2]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libblkid'
Making all in libmount
make[2]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libmount'
Making all in src
make[3]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libmount/src'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libmount/src'
make[3]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libmount'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libmount'
make[2]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/libmount'
Making all in man/ru
make[2]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/man/ru'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/man/ru'
Making all in login-utils
make[2]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/login-utils'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/login-utils'
Making all in misc-utils
make[2]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/misc-utils'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/misc-utils'
Making all in po
make[2]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/po'
make[2]: *** No rule to make target `all'. Stop.
make[2]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2/po'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/util-linux-2.21.2'
make: *** [all] Error 2
ERROR: oe_runmake failed
ERROR: Function failed: do_compile (see /media/sda3/yocto/poky-build/tmp/work/armv5te-poky-linux-gnueabi/util-linux-2.21.2-r6/temp/log.do_compile.31925 for further information)
6. I thought there might be e piece in the toolchain that was missing, so I did a "bitbake meta-toolchain", which resulted in the following error during the compilation of the nativesdk-gdbm package:
DEBUG: SITE files ['endian-little', 'bit-32', 'ix86-common', 'common-linux', 'common-glibc', 'i686-linux', 'common']
DEBUG: Executing shell function do_compile
NOTE: make -j 2
make all-recursive
make[1]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/i686-nativesdk-pokysdk-linux/nativesdk-gdbm-1.10-r3/gdbm-1.10'
Making all in po
make[2]: Entering directory `/media/sda3/yocto/poky-build/tmp/work/i686-nativesdk-pokysdk-linux/nativesdk-gdbm-1.10-r3/gdbm-1.10/po'
make[2]: *** No rule to make target `all'. Stop.
make[2]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/i686-nativesdk-pokysdk-linux/nativesdk-gdbm-1.10-r3/gdbm-1.10/po'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/media/sda3/yocto/poky-build/tmp/work/i686-nativesdk-pokysdk-linux/nativesdk-gdbm-1.10-r3/gdbm-1.10'
make: *** [all] Error 2
ERROR: oe_runmake failed
ERROR: Function failed: do_compile (see /media/sda3/yocto/poky-build/tmp/work/i686-nativesdk-pokysdk-linux/nativesdk-gdbm-1.10-r3/temp/log.do_compile.26132 for further information)
At this point I'm not sure why I'm seeing these errors and what is going wrong. I'd welcome any suggestions that would help me get the build to complete.
Thanks,
Bryan Evenson
_______________________________________________
poky mailing list
poky@yoctoproject.org
https://lists.yoctoproject.org/listinfo/poky
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Errors attempting to build AT91SAM9x5 BSP
2012-11-13 16:26 ` Bryan Evenson
@ 2012-11-13 17:10 ` Paul Eggleton
2012-11-13 17:46 ` Bryan Evenson
0 siblings, 1 reply; 8+ messages in thread
From: Paul Eggleton @ 2012-11-13 17:10 UTC (permalink / raw)
To: Bryan Evenson; +Cc: poky
On Tuesday 13 November 2012 11:26:08 Bryan Evenson wrote:
> I decided to start over with the stable danny tarball instead of using the
> Git repository. I've been able to build a core-image-minimal QEMU image
> and run it in QEMU. After that I created my new BSP using the yocto-bsp
> script and added my new BSP to the build/conf/bblayers.conf file as
> directed in the BSP Guide. However, now whenever I try to use bitbake for
> anything I get the error message "NOTE: Your conf/bblayers.conf has been
> automatically updated. Please re-run bitbake." I've tried incrementing the
> LCONF_VERSION variable in conf/bblayers.conf and incrementing the
> CONF_VERSION in conf/local.conf. I've also tried issuing "bitbake -f -c
> clean core-image-minimal" and I get the same error. The only way I've been
> able to use bitbake again is to remove the line for my new BSP from the
> BBLAYERS variable in conf/bblayers.conf.
What value was LCONF_VERSION at before you removed it? Also, could you send
your bblayers.conf file?
Thanks,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Errors attempting to build AT91SAM9x5 BSP
2012-11-13 17:10 ` Paul Eggleton
@ 2012-11-13 17:46 ` Bryan Evenson
2012-11-13 17:52 ` Paul Eggleton
0 siblings, 1 reply; 8+ messages in thread
From: Bryan Evenson @ 2012-11-13 17:46 UTC (permalink / raw)
To: Paul Eggleton; +Cc: poky
Here is the original bblayers.conf file before I started creating my BSP:
# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = "6"
BBPATH = "${TOPDIR}"
BBFILES ?= ""
BBLAYERS ?= " \
/media/sda3/yocto/poky-danny-8.0/meta \
/media/sda3/yocto/poky-danny-8.0/meta-yocto \
/media/sda3/yocto/poky-danny-8.0/meta-yocto-bsp \
"
And here is what it looks like after adding my BSP layer:
# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = "7"
BBPATH = "${TOPDIR}"
BBFILES ?= ""
BBLAYERS ?= " \
/media/sda3/yocto/poky-danny-8.0/meta \
/media/sda3/yocto/poky-danny-8.0/meta-yocto \
/media/sda3/yocto/poky-danny-8.0/meta-yocto-bsp \
/media/sda3/yocto/poky-danny-8.0/meta-intellihood-qemu \
"
Although, I just tried building again after changing the LCONF_VERSION back down to 6, and this time bitbake operates. I know I'd tried that before and it hadn't worked. The only difference that I can think of is that I've closed my terminal window and reopened it since my first posting and this one, which means I had to re-source the oe-init-build-env script. Is it possible that this was causing my problems from before?
Thanks,
Bryan
-----Original Message-----
From: Paul Eggleton [mailto:paul.eggleton@linux.intel.com]
Sent: Tuesday, November 13, 2012 12:11 PM
To: Bryan Evenson
Cc: poky@yoctoproject.org
Subject: Re: [poky] Errors attempting to build AT91SAM9x5 BSP
On Tuesday 13 November 2012 11:26:08 Bryan Evenson wrote:
> I decided to start over with the stable danny tarball instead of using
> the Git repository. I've been able to build a core-image-minimal QEMU
> image and run it in QEMU. After that I created my new BSP using the
> yocto-bsp script and added my new BSP to the build/conf/bblayers.conf
> file as directed in the BSP Guide. However, now whenever I try to use
> bitbake for anything I get the error message "NOTE: Your
> conf/bblayers.conf has been automatically updated. Please re-run
> bitbake." I've tried incrementing the LCONF_VERSION variable in
> conf/bblayers.conf and incrementing the CONF_VERSION in
> conf/local.conf. I've also tried issuing "bitbake -f -c clean
> core-image-minimal" and I get the same error. The only way I've been
> able to use bitbake again is to remove the line for my new BSP from the BBLAYERS variable in conf/bblayers.conf.
What value was LCONF_VERSION at before you removed it? Also, could you send your bblayers.conf file?
Thanks,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Errors attempting to build AT91SAM9x5 BSP
2012-11-13 17:46 ` Bryan Evenson
@ 2012-11-13 17:52 ` Paul Eggleton
2012-11-13 19:17 ` Bryan Evenson
0 siblings, 1 reply; 8+ messages in thread
From: Paul Eggleton @ 2012-11-13 17:52 UTC (permalink / raw)
To: Bryan Evenson; +Cc: poky
On Tuesday 13 November 2012 12:46:42 Bryan Evenson wrote:
> Here is the original bblayers.conf file before I started creating my BSP:
>
> # LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
> # changes incompatibly
> LCONF_VERSION = "6"
>
> BBPATH = "${TOPDIR}"
> BBFILES ?= ""
>
> BBLAYERS ?= " \
> /media/sda3/yocto/poky-danny-8.0/meta \
> /media/sda3/yocto/poky-danny-8.0/meta-yocto \
> /media/sda3/yocto/poky-danny-8.0/meta-yocto-bsp \
> "
>
> And here is what it looks like after adding my BSP layer:
>
> # LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
> # changes incompatibly
> LCONF_VERSION = "7"
>
> BBPATH = "${TOPDIR}"
> BBFILES ?= ""
>
> BBLAYERS ?= " \
> /media/sda3/yocto/poky-danny-8.0/meta \
> /media/sda3/yocto/poky-danny-8.0/meta-yocto \
> /media/sda3/yocto/poky-danny-8.0/meta-yocto-bsp \
> /media/sda3/yocto/poky-danny-8.0/meta-intellihood-qemu \
> "
>
> Although, I just tried building again after changing the LCONF_VERSION back
> down to 6, and this time bitbake operates. I know I'd tried that before
> and it hadn't worked. The only difference that I can think of is that I've
> closed my terminal window and reopened it since my first posting and this
> one, which means I had to re-source the oe-init-build-env script. Is it
> possible that this was causing my problems from before?
You shouldn't increase LCONF_VERSION unless LAYER_CONF_VERSION increases, and
certainly it shouldn't be increased beyond the value of LAYER_CONF_VERSION
(currently this is 6 in meta-yocto, 5 in OE-Core); why it would be telling you
it had updated it if you did do that I don't know, that's certainly not
intended behaviour.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Errors attempting to build AT91SAM9x5 BSP
2012-11-13 17:52 ` Paul Eggleton
@ 2012-11-13 19:17 ` Bryan Evenson
2012-11-15 11:03 ` Paul Eggleton
2012-11-19 16:35 ` Bryan Evenson
0 siblings, 2 replies; 8+ messages in thread
From: Bryan Evenson @ 2012-11-13 19:17 UTC (permalink / raw)
To: Paul Eggleton; +Cc: poky
Paul,
Thanks for the information. From my reading of the BSP manual I'd thought I was supposed to increment the LCONF_VERSION each time I made a change to the bblayers.conf file; I appreciate the clarification.
I searched for the error message I was getting, and I think it was originating in this section of sanity.bbclass:
# Check bblayers.conf is valid
current_lconf = sanity_data.getVar('LCONF_VERSION', True)
lconf_version = sanity_data.getVar('LAYER_CONF_VERSION', True)
if current_lconf != lconf_version:
try:
bb.build.exec_func("check_bblayers_conf", sanity_data)
if sanity_data.getVar("SANITY_USE_EVENTS", True) == "1":
bb.event.fire(bb.event.SanityCheckFailed("Your conf/bblayers.conf has been automatically updated. Please close and re-run."), sanity_data)
return
else:
bb.note("Your conf/bblayers.conf has been automatically updated. Please re-run %s." % os.path.basename(sys.argv[0]))
sys.exit(0)
except Exception:
messages = messages + "Your version of bblayers.conf was generated from an older version of bblayers.conf.sample and there have been updates made to this file. Please compare the two files and merge any changes before continuing.\nMatching the version numbers will remove this message.\n\"meld conf/bblayers.conf ${COREBASE}/meta*/conf/bblayers.conf.sample\" is a good way to visualise the changes.\n"
Would it be helpful if the current_lconf != lconf_version check changed to have different messages when current_lconf > lconf_version and when current_lcong < lconf_version?
Thanks,
Bryan
-----Original Message-----
From: Paul Eggleton [mailto:paul.eggleton@linux.intel.com]
Sent: Tuesday, November 13, 2012 12:53 PM
To: Bryan Evenson
Cc: poky@yoctoproject.org
Subject: Re: [poky] Errors attempting to build AT91SAM9x5 BSP
On Tuesday 13 November 2012 12:46:42 Bryan Evenson wrote:
> Here is the original bblayers.conf file before I started creating my BSP:
>
> # LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
> # changes incompatibly
> LCONF_VERSION = "6"
>
> BBPATH = "${TOPDIR}"
> BBFILES ?= ""
>
> BBLAYERS ?= " \
> /media/sda3/yocto/poky-danny-8.0/meta \
> /media/sda3/yocto/poky-danny-8.0/meta-yocto \
> /media/sda3/yocto/poky-danny-8.0/meta-yocto-bsp \
> "
>
> And here is what it looks like after adding my BSP layer:
>
> # LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
> # changes incompatibly
> LCONF_VERSION = "7"
>
> BBPATH = "${TOPDIR}"
> BBFILES ?= ""
>
> BBLAYERS ?= " \
> /media/sda3/yocto/poky-danny-8.0/meta \
> /media/sda3/yocto/poky-danny-8.0/meta-yocto \
> /media/sda3/yocto/poky-danny-8.0/meta-yocto-bsp \
> /media/sda3/yocto/poky-danny-8.0/meta-intellihood-qemu \
> "
>
> Although, I just tried building again after changing the LCONF_VERSION back
> down to 6, and this time bitbake operates. I know I'd tried that before
> and it hadn't worked. The only difference that I can think of is that I've
> closed my terminal window and reopened it since my first posting and this
> one, which means I had to re-source the oe-init-build-env script. Is it
> possible that this was causing my problems from before?
You shouldn't increase LCONF_VERSION unless LAYER_CONF_VERSION increases, and
certainly it shouldn't be increased beyond the value of LAYER_CONF_VERSION
(currently this is 6 in meta-yocto, 5 in OE-Core); why it would be telling you
it had updated it if you did do that I don't know, that's certainly not
intended behaviour.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Errors attempting to build AT91SAM9x5 BSP
2012-11-13 19:17 ` Bryan Evenson
@ 2012-11-15 11:03 ` Paul Eggleton
2012-11-19 16:35 ` Bryan Evenson
1 sibling, 0 replies; 8+ messages in thread
From: Paul Eggleton @ 2012-11-15 11:03 UTC (permalink / raw)
To: Bryan Evenson; +Cc: poky
On Tuesday 13 November 2012 14:17:06 Bryan Evenson wrote:
> Thanks for the information. From my reading of the BSP manual I'd thought I
> was supposed to increment the LCONF_VERSION each time I made a change to
> the bblayers.conf file; I appreciate the clarification.
Could you suggest a change to the BSP manual that would help avoid this
confusion?
> I searched for the error message I was getting, and I think it was
> originating in this section of sanity.bbclass:
>
> # Check bblayers.conf is valid
> current_lconf = sanity_data.getVar('LCONF_VERSION', True)
> lconf_version = sanity_data.getVar('LAYER_CONF_VERSION', True)
> if current_lconf != lconf_version:
> try:
> bb.build.exec_func("check_bblayers_conf", sanity_data)
> if sanity_data.getVar("SANITY_USE_EVENTS", True) == "1":
> bb.event.fire(bb.event.SanityCheckFailed("Your
> conf/bblayers.conf has been automatically updated. Please close and
> re-run."), sanity_data) return
> else:
> bb.note("Your conf/bblayers.conf has been automatically
> updated. Please re-run %s." % os.path.basename(sys.argv[0])) sys.exit(0)
> except Exception:
> messages = messages + "Your version of bblayers.conf was
> generated from an older version of bblayers.conf.sample and there have been
> updates made to this file. Please compare the two files and merge any
> changes before continuing.\nMatching the version numbers will remove this
> message.\n\"meld conf/bblayers.conf
> ${COREBASE}/meta*/conf/bblayers.conf.sample\" is a good way to visualise
> the changes.\n"
Right, I guess (without having tested it recently) what I expected to happen
was the check_bblayers_conf function would have raised an exception if it
couldn't do anything with the file; currently it doesn't.
> Would it be helpful if the current_lconf != lconf_version check changed to
> have different messages when current_lconf > lconf_version and when
> current_lcong < lconf_version?
I think that would be a good idea, yes.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Errors attempting to build AT91SAM9x5 BSP
2012-11-13 19:17 ` Bryan Evenson
2012-11-15 11:03 ` Paul Eggleton
@ 2012-11-19 16:35 ` Bryan Evenson
1 sibling, 0 replies; 8+ messages in thread
From: Bryan Evenson @ 2012-11-19 16:35 UTC (permalink / raw)
To: poky, Paul Eggleton
All,
I think I'm building an image that includes my BSP, but I can't get the image to run under QEMU. If I don't include my BSP in the BBLAYERS variable in bblayers.conf, then the resulting built image runs under QEMU. Here's the steps I took to create a build the BSP.
1. Downloaded and extracted the poky-danny-8.0 tarball for my Yocto Project setup.
1. From my Source Directory, I invoked the BSP builder by calling "yocto-bsp create foo-qemu qemu"
2. Selected option 3 (ARM) for the qemu architecture.
3. Selected "y" to use the default 3.4 kernel.
4. Selected "y" to start a new branch for this BSP.
5. Selected "1" to base the machine on the arm-versatile-926ejs branch.
6. Selected "y" to include SMP support.
7. Selected "n" to indicate the BSP does not have a touchscreen.
8. Selected "n" to indicate the BSP does not have a keyboard.
9. Copied the configuration from tmp/sysroots/qemuarm/usr/src/kernel/arch/arm/configs/vexpress_defconfig as meta-foo-qemu/recipes-kernel/linux/files/foo-qemu.cfg.
10. Added my new BSP to the bblayers.conf file.
11. Called "bitbake -c clean linux-yocto && bitbake core-image-minimal" to rebuild the image with my BSP. My BSP shows up in the Bitbake configuration parameters.
12. Run my image by calling "runqemu qemuarm". A few details are printed out for the QEMU setup, a new window is launched for QEMU but the QEMU window remains blank.
If I remove my new BSP from bblayers.conf and redo steps 11 and 12, then the image boots just fine under QEMU. Are there some steps I'm missing in configuring my BSP?
Thanks,
Bryan
> -----Original Message-----
> From: poky-bounces@yoctoproject.org [mailto:poky-
> bounces@yoctoproject.org] On Behalf Of Bryan Evenson
> Sent: Tuesday, November 13, 2012 2:17 PM
> To: Paul Eggleton
> Cc: poky@yoctoproject.org
> Subject: Re: [poky] Errors attempting to build AT91SAM9x5 BSP
>
> Paul,
>
> Thanks for the information. From my reading of the BSP manual I'd
> thought I was supposed to increment the LCONF_VERSION each time I made
> a change to the bblayers.conf file; I appreciate the clarification.
>
> I searched for the error message I was getting, and I think it was
> originating in this section of sanity.bbclass:
>
> # Check bblayers.conf is valid
> current_lconf = sanity_data.getVar('LCONF_VERSION', True)
> lconf_version = sanity_data.getVar('LAYER_CONF_VERSION', True)
> if current_lconf != lconf_version:
> try:
> bb.build.exec_func("check_bblayers_conf", sanity_data)
> if sanity_data.getVar("SANITY_USE_EVENTS", True) == "1":
> bb.event.fire(bb.event.SanityCheckFailed("Your
> conf/bblayers.conf has been automatically updated. Please close and re-
> run."), sanity_data)
> return
> else:
> bb.note("Your conf/bblayers.conf has been automatically
> updated. Please re-run %s." % os.path.basename(sys.argv[0]))
> sys.exit(0)
> except Exception:
> messages = messages + "Your version of bblayers.conf was
> generated from an older version of bblayers.conf.sample and there have
> been updates made to this file. Please compare the two files and merge
> any changes before continuing.\nMatching the version numbers will
> remove this message.\n\"meld conf/bblayers.conf
> ${COREBASE}/meta*/conf/bblayers.conf.sample\" is a good way to
> visualise the changes.\n"
>
> Would it be helpful if the current_lconf != lconf_version check changed
> to have different messages when current_lconf > lconf_version and when
> current_lcong < lconf_version?
>
> Thanks,
> Bryan
>
> -----Original Message-----
> From: Paul Eggleton [mailto:paul.eggleton@linux.intel.com]
> Sent: Tuesday, November 13, 2012 12:53 PM
> To: Bryan Evenson
> Cc: poky@yoctoproject.org
> Subject: Re: [poky] Errors attempting to build AT91SAM9x5 BSP
>
> On Tuesday 13 November 2012 12:46:42 Bryan Evenson wrote:
> > Here is the original bblayers.conf file before I started creating my
> BSP:
> >
> > # LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
> #
> > changes incompatibly LCONF_VERSION = "6"
> >
> > BBPATH = "${TOPDIR}"
> > BBFILES ?= ""
> >
> > BBLAYERS ?= " \
> > /media/sda3/yocto/poky-danny-8.0/meta \
> > /media/sda3/yocto/poky-danny-8.0/meta-yocto \
> > /media/sda3/yocto/poky-danny-8.0/meta-yocto-bsp \
> > "
> >
> > And here is what it looks like after adding my BSP layer:
> >
> > # LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
> #
> > changes incompatibly LCONF_VERSION = "7"
> >
> > BBPATH = "${TOPDIR}"
> > BBFILES ?= ""
> >
> > BBLAYERS ?= " \
> > /media/sda3/yocto/poky-danny-8.0/meta \
> > /media/sda3/yocto/poky-danny-8.0/meta-yocto \
> > /media/sda3/yocto/poky-danny-8.0/meta-yocto-bsp \
> > /media/sda3/yocto/poky-danny-8.0/meta-intellihood-qemu \
> > "
> >
> > Although, I just tried building again after changing the
> LCONF_VERSION
> > back down to 6, and this time bitbake operates. I know I'd tried
> that
> > before and it hadn't worked. The only difference that I can think of
> > is that I've closed my terminal window and reopened it since my first
> > posting and this one, which means I had to re-source the
> > oe-init-build-env script. Is it possible that this was causing my
> problems from before?
>
> You shouldn't increase LCONF_VERSION unless LAYER_CONF_VERSION
> increases, and certainly it shouldn't be increased beyond the value of
> LAYER_CONF_VERSION (currently this is 6 in meta-yocto, 5 in OE-Core);
> why it would be telling you it had updated it if you did do that I
> don't know, that's certainly not intended behaviour.
>
> Cheers,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2012-11-19 16:35 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-11-09 18:27 Errors attempting to build AT91SAM9x5 BSP Bryan Evenson
2012-11-13 16:26 ` Bryan Evenson
2012-11-13 17:10 ` Paul Eggleton
2012-11-13 17:46 ` Bryan Evenson
2012-11-13 17:52 ` Paul Eggleton
2012-11-13 19:17 ` Bryan Evenson
2012-11-15 11:03 ` Paul Eggleton
2012-11-19 16:35 ` Bryan Evenson
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.