Date   

How to update Git clone when rebuilding

Tino Breddin <tb@...>
 

Hi,

I've noticed that bitbake won't update a Git checkout of an
application referenced through a recipe when running a follow-up build.

Is there some way to tell bitbake to check whether the remote Git
repository provides updates which should trigger a rebuild of the
application?

Cheers,
Tino


[PATCH] Fix typo in kvm capability detection in runqemu

Björn Stenberg <bjorn@...>
 

Signed-off-by: Björn Stenberg <bjst@...>
---
diff --git a/scripts/runqemu b/scripts/runqemu
index fb7ac56..fc7d749 100755
--- a/scripts/runqemu
+++ b/scripts/runqemu
@@ -155,7 +155,7 @@ while true; do
;;
"kvm")
KVM_ENABLED="yes"
- KVM_CAPABLE=`grep -q 'vmx\|smx' /proc/cpuinfo && echo 1`
+ KVM_CAPABLE=`grep -q 'vmx\|svm' /proc/cpuinfo && echo 1`
;;
"") break ;;
*)

--
Björn


Re: How to use JRE (Java Runtime) in Yocto Projects

Raul Mu?oz
 

Paul, Thanks for all help.

I did what you told, I created a new project with all metas in danny branch:
meta-fsl-arm$ git branch 
* local/origin/danny
  master

meta-openembedded$ git branch 
* local/origin/danny
  master

poky$ git branch 
* local/origin/danny
  master

meta-java$ git branch 
* master

In Local config I changed just the machine for
MACHINE ?= "imx28evk"

And added the lines needed for java

PREFERRED_PROVIDER_virtual/java-native = "jamvm-native"
PREFERRED_PROVIDER_virtual/javac-native = "ecj-bootstrap-native"

PREFERRED_VERSION_openjdk-6-jre = "6b24-1.11.5"
PREFERRED_VERSION_icedtea6-native = "1.8.11"

I have changed my bblayes for:

BBLAYERS ?= " \
  /media/dados/prjs/imx-JAVA/philinux/poky/meta \
  /media/dados/prjs/imx-JAVA/philinux/poky/meta-yocto \
  /media/dados/prjs/imx-JAVA/philinux/poky/meta-yocto-bsp \
  /media/dados/prjs/imx-JAVA/philinux/meta-fsl-arm \
  /media/dados/prjs/imx-JAVA/philinux/meta-openembedded/meta-oe \
  /media/dados/prjs/imx-JAVA/philinux/meta-java \
  "

Now I think that every things  work better, but I get a error that I dont know how to solve:


raul@phi04:/media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java$ bitbake openjdk-6-jre
WARNING: Unable to get checksum for barebox SRC_URI entry defconfig: file could not be found                                          | ETA:  00:00:25
Parsing recipes: 100% |###############################################################################################################| Time: 00:00:48
Parsing of 1320 .bb files complete (0 cached, 1320 parsed). 1706 targets, 70 skipped, 0 masked, 0 errors.

Build Configuration:
BB_VERSION        = "1.16.0"
TARGET_ARCH       = "arm"
TARGET_OS         = "linux-gnueabi"
MACHINE           = "imx28evk"
DISTRO            = "poky"
DISTRO_VERSION    = "1.3"
TUNE_FEATURES     = "armv5 dsp thumb arm926ejs"
TARGET_FPU        = "soft"
meta              
meta-yocto        
meta-yocto-bsp    = "local/origin/danny:bf909b267498dbab4d7695c26b0dce903ac8b6b0"
meta-fsl-arm      = "local/origin/danny:fdc178fb22b3370d3a2cde66b6a4171627dd4721"
meta-oe           = "local/origin/danny:f026e96295da101bb715858bc8705de7e4a33992"
meta-java         = "master:2eb6d2643e3833657cfd278b0502945df99ee18a"

NOTE: Resolving any missing task queue dependencies
NOTE: multiple providers are available for jpeg (jpeg, libjpeg-turbo)
NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg
NOTE: multiple providers are available for runtime java2-runtime (openjdk-6-jre, jamvm, openjdk-7-jre)
NOTE: consider defining a PREFERRED_PROVIDER entry to match java2-runtime
NOTE: multiple providers are available for runtime java2-vm (openjdk-6-jre, openjdk-7-jre)
NOTE: consider defining a PREFERRED_PROVIDER entry to match java2-vm
NOTE: multiple providers are available for jpeg-native (jpeg-native, libjpeg-turbo-native)
NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg-native
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: Function failed: do_compile (see /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/temp/log.do_compile.23542 for further information)
ERROR: Logfile of failure stored in: /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/temp/log.do_compile.23542
Log data follows:
| 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 4
| /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/sysroots/i686-linux/usr/bin/cmake -H/media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8 -B/media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build --check-build-system CMakeFiles/Makefile.cmake 0
| /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/sysroots/i686-linux/usr/bin/cmake -E cmake_progress_start /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build/CMakeFiles /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build/CMakeFiles/progress.marks
| make -f CMakeFiles/Makefile2 all
| make[1]: Entering directory `/media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build'
| make -f lib/System/CMakeFiles/LLVMSystem.dir/build.make lib/System/CMakeFiles/LLVMSystem.dir/depend
| make -f lib/Transforms/Hello/CMakeFiles/LLVMHello.dir/build.make lib/Transforms/Hello/CMakeFiles/LLVMHello.dir/depend
| make -f utils/count/CMakeFiles/count.dir/build.make utils/count/CMakeFiles/count.dir/depend
| make -f tools/bugpoint-passes/CMakeFiles/BugpointPasses.dir/build.make tools/bugpoint-passes/CMakeFiles/BugpointPasses.dir/depend
| make[2]: Entering directory `/media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build'
| cd /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build && /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/sysroots/i686-linux/usr/bin/cmake -E cmake_depends "Unix Makefiles" /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8 /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/lib/System /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build/lib/System /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build/lib/System/CMakeFiles/LLVMSystem.dir/DependInfo.cmake --color=
| make[2]: Entering directory `/media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build'
| cd /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build && /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/sysroots/i686-linux/usr/bin/cmake -E cmake_depends "Unix Makefiles" /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8 /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/lib/Transforms/Hello /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build/lib/Transforms/Hello /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build/lib/Transforms/Hello/CMakeFiles/LLVMHello.dir/DependInfo.cmake --color=
| make[2]: Entering directory `/media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build'
| cd /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build && /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/sysroots/i686-linux/usr/bin/cmake -E cmake_depends "Unix Makefiles" /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8 /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/tools/bugpoint-passes /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build/tools/bugpoint-passes /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build/tools/bugpoint-passes/CMakeFiles/BugpointPasses.dir/DependInfo.cmake --color=
| make[2]: Leaving directory `/media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build'


...
...
...



/CMakeFiles/EnhancedDisassembly.dir/DependInfo.cmake --color=
| make[2]: Entering directory `/media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build'
| cd /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build && /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/sysroots/i686-linux/usr/bin/cmake -E cmake_depends "Unix Makefiles" /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8 /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/tools/bugpoint /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build/tools/bugpoint /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build/tools/bugpoint/CMakeFiles/bugpoint.dir/DependInfo.cmake --color=
| make[2]: Leaving directory `/media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build'
| make -f tools/edis/CMakeFiles/EnhancedDisassembly.dir/build.make tools/edis/CMakeFiles/EnhancedDisassembly.dir/build
| make[2]: Entering directory `/media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build'
| make[2]: Nothing to be done for `tools/edis/CMakeFiles/EnhancedDisassembly.dir/build'.
| make[2]: Leaving directory `/media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build'
| /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/sysroots/i686-linux/usr/bin/cmake -E cmake_progress_report /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build/CMakeFiles
| [ 98%] Built target EnhancedDisassembly
| make[2]: Leaving directory `/media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build'
| make -f tools/bugpoint/CMakeFiles/bugpoint.dir/build.make tools/bugpoint/CMakeFiles/bugpoint.dir/build
| make[2]: Entering directory `/media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build'
| make[2]: Nothing to be done for `tools/bugpoint/CMakeFiles/bugpoint.dir/build'.
| make[2]: Leaving directory `/media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build'
| /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/sysroots/i686-linux/usr/bin/cmake -E cmake_progress_report /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build/CMakeFiles  88
| [100%] Built target bugpoint
| ../../lib/libLLVMARMCodeGen.a(ARMISelLowering.cpp.o): In function `llvm::ARMTargetLowering::LowerCall(llvm::SDValue, llvm::SDValue, llvm::CallingConv::ID, bool, bool&, llvm::SmallVectorImpl<llvm::ISD::OutputArg> const&, llvm::SmallVectorImpl<llvm::SDValue> const&, llvm::SmallVectorImpl<llvm::ISD::InputArg> const&, llvm::DebugLoc, llvm::SelectionDAG&, llvm::SmallVectorImpl<llvm::SDValue>&) const':
| /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/lib/Target/ARM/ARMISelLowering.cpp:1293: undefined reference to `getPointerToNamedFunctionOrNull'
| ../../lib/libLLVMARMAsmPrinter.a(ARMInstPrinter.cpp.o): In function `llvm::ARMInstPrinter::~ARMInstPrinter()':
| /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/lib/Target/ARM/AsmPrinter/ARMInstPrinter.h:22: undefined reference to `llvm::MCInstPrinter::~MCInstPrinter()'
| ../../lib/libLLVMARMAsmPrinter.a(ARMInstPrinter.cpp.o): In function `~ARMInstPrinter':
| /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/lib/Target/ARM/AsmPrinter/ARMInstPrinter.h:22: undefined reference to `llvm::MCInstPrinter::~MCInstPrinter()'
| ../../lib/libLLVMARMAsmPrinter.a(ARMInstPrinter.cpp.o):(.data.rel.ro+0x8): undefined reference to `typeinfo for llvm::MCInstPrinter'
| ../../lib/libLLVMARMAsmPrinter.a(ARMInstPrinter.cpp.o):(.data.rel.ro+0x24): undefined reference to `llvm::MCInstPrinter::getOpcodeName(unsigned int) const'
| collect2: error: ld returned 1 exit status
| make[2]: *** [bin/llvm-mc] Error 1
| make[2]: Leaving directory `/media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build'
| make[1]: *** [tools/llvm-mc/CMakeFiles/llvm-mc.dir/all] Error 2
| make[1]: Leaving directory `/media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/llvm-2.8/build'
| make: *** [all] Error 2
| ERROR: oe_runmake failed
| ERROR: Function failed: do_compile (see /media/dados/prjs/imx-JAVA/philinux/philinux-imx28-java/tmp/work/armv5te-poky-linux-gnueabi/llvm2.8-2.8-r2.1/temp/log.do_compile.23542 for further information)
ERROR: Task 353 (/media/dados/prjs/imx-JAVA/philinux/meta-java/recipes-core/llvm/llvm2.8_2.8.bb, do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 1646 tasks of which 1634 didn't need to be rerun and 1 failed.
Waiting for 0 running tasks to finish:

Summary: 1 task failed:
  /media/dados/prjs/imx-JAVA/philinux/meta-java/recipes-core/llvm/llvm2.8_2.8.bb, do_compile
Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.


Some one can Help me?

I thing that there is some thing with this:

| ../../lib/libLLVMARMAsmPrinter.a(ARMInstPrinter.cpp.o):(.data.rel.ro+0x8): undefined reference to `typeinfo for llvm::MCInstPrinter'
| ../../lib/libLLVMARMAsmPrinter.a(ARMInstPrinter.cpp.o):(.data.rel.ro+0x24): undefined reference to `llvm::MCInstPrinter::getOpcodeName(unsigned int) const'



2012/12/19 Paul Eggleton <paul.eggleton@...>

On Wednesday 19 December 2012 15:31:42 Raul Rosetto Munoz wrote:
> raul@phi04:/home/prjs/poky$ git branch
> * local/origin/denzil

There doesn't seem to be a denzil branch for meta-java and it's likely the
error you're receiving is because the master branch of meta-java is
incompatible with the denzil release. I would suggest updating to the danny
release, or alternatively you'll need to modify meta-java to be compatible
with denzil (i.e. you'll have to match indenting in python functions such as
populate_packages_prepend).

Cheers,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre



--
Raul Rosetto Muñoz


Re: An added task is not run by bitbake, why is that ?

Biao <huanmateme@...>
 

Now i got it, when i issue "bitbake dummy", it will only try to do a "build" task, which is not DEPENDS on my task.
Thanks,

At 2012-12-20 15:28:31,Biao <huanmateme@...> wrote:
Hi All,

 An added task is not run by bitbake, why is that ?
The meta-test layer setup is ok, you can forget this.

After i issue bitbake dummy, i found that it runs succeed with the tasks in base.bbclass, but my dummy1 is not run, why is that?

meta-test/dummy/dummy.0.0.bb
<pre>
DESCRIPTION = "A simply dummy package"

do_dummy0 () {
        bbnote "Doing Dummy0."
}

do_dummy1 () {
        bbnote "Doing Dummy1."
}

do_dummy2 () {
        bbnote "Doing Dummy2."
}

addtask dummy1 before do_dummy2 after do_dummy0
</pre>

Thanks,
Biao


An added task is not run by bitbake, why is that ?

Biao <huanmateme@...>
 

Hi All,

 An added task is not run by bitbake, why is that ?
The meta-test layer setup is ok, you can forget this.

After i issue bitbake dummy, i found that it runs succeed with the tasks in base.bbclass, but my dummy1 is not run, why is that?

meta-test/dummy/dummy.0.0.bb
<pre>
DESCRIPTION = "A simply dummy package"

do_dummy0 () {
        bbnote "Doing Dummy0."
}

do_dummy1 () {
        bbnote "Doing Dummy1."
}

do_dummy2 () {
        bbnote "Doing Dummy2."
}

addtask dummy1 before do_dummy2 after do_dummy0
</pre>

Thanks,
Biao


Re: Where does the bitbake get the variable "TOPDIR"

Biao <huanmateme@...>
 


At 2012-12-19 00:35:13,"Eren Türkay" <eren@...> wrote: >On Tue, Dec 18, 2012 at 08:28:32PM +0800, Biao wrote: >> >http://hambedded.org/blog/2012/11/24/from-bitbake-hello-world-to-an-image/ >> I will try to give some feedback after finishing the reading. >> But for now, there are some silly questions: >> 1. There is a base_do_fetch() {}, I did not find the explanation of the keyword of 'base' in the manual, do i miss something? > >I don't know the internals of bitbake on that level but as far as I >understand, bitbake uses the name of the bbclass file as a prefix in the >function names for the sake of abstraction. So, as in autotools.bbclass, >the tasks defined in base.bbclass gets prefixes with "base_" keyword. >Probably, it's related with mapping the function names when 'inherit' >keyword is used.
I agree it seems a prefix is mandatory when working with EXPORT_FUNCTIONS.
>
>I'm not clear on this topic either. A hand from an experienced bitbake
>guru would be really helpful here. The type of abstraction in bitbake
>should be explained in detail as well as how EXPORT_FUNCTION works.
>
>Any volunteers?
>
>> 2. There is 'bb.note' and 'bbnote' in the code example, is it a type-mistake or something else?
>
>No, this is not a mistake. You can use python as well as shell functions
>in bitbake recipes and classes. See 'python' keyword in function
>definitons where bb.note is used. That's why python function "bb.note()"
>is used to print log information. Without python keyword, the bitbake
>function is treated as shell.
>
Ok, so the bb.note is a python provided functions, which is missing from the docs.
>Regards,
>Eren
>
>-- 
>    . 73! DE TA1AET
>      http://linkedin.com/in/erenturkay


Re: [PATCH 5/5] scripts/lib/bsp/engine.py: refactor bsp-creation code

Darren Hart <dvhart@...>
 

On 12/17/2012 09:51 AM, tom.zanussi@... wrote:
From: Tom Zanussi <tom.zanussi@...>

This does a bit of refactoring of the bsp-generation code to make it
generically reusable for generating non-bsp layers.

The first user remains the existing yocto-bsp tool; these changes
allow a second user, the new yocto-layer tool, to use the same code.
Aha, this is what I was looking for earlier - sorry my email search
pattern dropped this patch initially.

Just a cursory review, but looks good to me.

--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel


Re: [PATCH 4/5] yocto-layer: add 'layer' template data

Darren Hart <dvhart@...>
 

On 12/17/2012 09:51 AM, tom.zanussi@... wrote:
From: Tom Zanussi <tom.zanussi@...>

Add a 'layer' target containing all the data that will be used to
generate a generic yocto layer.

Signed-off-by: Tom Zanussi <tom.zanussi@...>
---
Great stuff Tom, only one nit below:

new file mode 100644
index 0000000..90ce90e
--- /dev/null
+++ "b/scripts/lib/bsp/substrate/target/arch/layer/{{ if create_example_recipe == \"y\": }} recipes-example/example/{{=example_recipe_name}}-0.1/helloworld.c"
@@ -0,0 +1,6 @@
+#include <stdio.h>
+
+int main(int argc, char **argv)
+{
+ printf("Hello World!\n");
If you specify a return type of int, you should be returning one:

return 0;

:-)

+}

Looks good otherwise.


--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel


Re: [PATCH 2/5] yocto-layer: new script

Darren Hart <dvhart@...>
 

On 12/17/2012 09:51 AM, tom.zanussi@... wrote:
From: Tom Zanussi <tom.zanussi@...>

Implementation of the 'yocto-layer' command-line tool, for creating
generic layers and listing their input properties.
No specific comments below, looks good.

Would the final version also include a removal of similar code from
yocto-bsp, such that yocto-bsp would call yocto-layer? I'm thinking
about reducing code duplication. I guess not as this is mostly just
argument parsing and all the logic is already abstracted into bsp.engine?

Thanks,

Darren


Signed-off-by: Tom Zanussi <tom.zanussi@...>
---
scripts/yocto-layer | 142 ++++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 142 insertions(+)
create mode 100755 scripts/yocto-layer

diff --git a/scripts/yocto-layer b/scripts/yocto-layer
new file mode 100755
index 0000000..f759275
--- /dev/null
+++ b/scripts/yocto-layer
@@ -0,0 +1,142 @@
+#!/usr/bin/env python
+# ex:ts=4:sw=4:sts=4:et
+# -*- tab-width: 4; c-basic-offset: 4; indent-tabs-mode: nil -*-
+#
+# Copyright (c) 2012, Intel Corporation.
+# All rights reserved.
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License version 2 as
+# published by the Free Software Foundation.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License along
+# with this program; if not, write to the Free Software Foundation, Inc.,
+# 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+#
+# DESCRIPTION
+# 'yocto-layer' is the Yocto Tool that helps users create a new Yocto
+# layer. Invoking it without any arguments will display help screens
+# for the 'yocto-layer' command and list the available 'yocto-layer'
+# subcommands. Invoking a subcommand without any arguments will
+# likewise display help screens for the specified subcommand. Please
+# use that interface for detailed help.
+#
+# AUTHORS
+# Tom Zanussi <tom.zanussi (at] intel.com>
+#
+
+__version__ = "0.1.0"
+
+import os
+import sys
+import optparse
+import logging
+
+scripts_path = os.path.abspath(os.path.dirname(os.path.abspath(sys.argv[0])))
+lib_path = scripts_path + '/lib'
+sys.path = sys.path + [lib_path]
+
+from bsp.help import *
+from bsp.engine import *
+
+
+def yocto_layer_create_subcommand(args, usage_str):
+ """
+ Command-line handling for layer creation. The real work is done by
+ bsp.engine.yocto_layer_create()
+ """
+ parser = optparse.OptionParser(usage = usage_str)
+
+ parser.add_option("-o", "--outdir", dest = "outdir", action = "store",
+ help = "name of layer dir to create")
+ parser.add_option("-i", "--infile", dest = "properties_file", action = "store",
+ help = "name of file containing the values for layer input properties as a JSON file")
+ parser.add_option("-c", "--codedump", dest = "codedump", action = "store_true",
+ default = False, help = "dump the generated code to layergen.out")
+ (options, args) = parser.parse_args(args)
+
+ if len(args) != 1:
+ logging.error("Wrong number of arguments, exiting\n")
+ parser.print_help()
+ sys.exit(1)
+
+ layer_name = args[0]
+
+ if options.outdir:
+ layer_output_dir = options.outdir
+ else:
+ layer_output_dir = "meta-" + layer_name
+
+ yocto_layer_create(layer_name, scripts_path, layer_output_dir, options.codedump, options.properties_file)
+
+
+def yocto_layer_list_subcommand(args, usage_str):
+ """
+ Command-line handling for listing available layer properties and
+ values. The real work is done by bsp.engine.yocto_layer_list()
+ """
+ parser = optparse.OptionParser(usage = usage_str)
+
+ parser.add_option("-o", "--outfile", action = "store", dest = "properties_file",
+ help = "dump the possible values for layer properties to a JSON file")
+
+ (options, args) = parser.parse_args(args)
+
+ if not yocto_layer_list(args, scripts_path, options.properties_file):
+ logging.error("Bad list arguments, exiting\n")
+ parser.print_help()
+ sys.exit(1)
+
+
+subcommands = {
+ "create": [yocto_layer_create_subcommand,
+ yocto_layer_create_usage,
+ yocto_layer_create_help],
+ "list": [yocto_layer_list_subcommand,
+ yocto_layer_list_usage,
+ yocto_layer_list_help],
+}
+
+
+def start_logging(loglevel):
+ logging.basicConfig(filname = 'yocto-layer.log', filemode = 'w', level=loglevel)
+
+
+def main():
+ parser = optparse.OptionParser(version = "yocto-layer version %s" % __version__,
+ usage = yocto_layer_usage)
+
+ parser.disable_interspersed_args()
+ parser.add_option("-D", "--debug", dest = "debug", action = "store_true",
+ default = False, help = "output debug information")
+
+ (options, args) = parser.parse_args()
+
+ loglevel = logging.INFO
+ if options.debug:
+ loglevel = logging.DEBUG
+ start_logging(loglevel)
+
+ if len(args):
+ if args[0] == "help":
+ if len(args) == 1:
+ parser.print_help()
+ sys.exit(1)
+
+ invoke_subcommand(args, parser, yocto_layer_help_usage, subcommands)
+
+
+if __name__ == "__main__":
+ try:
+ ret = main()
+ except Exception:
+ ret = 1
+ import traceback
+ traceback.print_exc(5)
+ sys.exit(ret)
+
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel


Re: [PATCH 0/5] RFC: new 'yocto-layer' tool for creating generic Yocto layers

Darren Hart <dvhart@...>
 

On 12/17/2012 09:51 AM, tom.zanussi@... wrote:
From: Tom Zanussi <tom.zanussi@...>

Since I've been doing kind of similar work lately for the 'custom kernel'
support for yocto-bsp and have gotten several requests lately (mainly
from Darren in support of the new kernel documentation) for something
like this, I decided to just go ahead and try to quickly implement a
general-purpose layer-generation tool based on the BSP-generation code
used in the yocto-bsp tool.

There's actually an enhancement request bug for this already in the
Yocto bugzilla, but it doesn't contain many details:

Bug 3094 - Add a layer generation tool:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=3094

So anyway, this is my initial take on what that bug means. It's an RFC for
a couple reasons, first that I'd like to get comments on whether this is
actually what's needed for a 'layer generation tool', and second, because I
still need to do some cleanup of the refactored code, but don't want to
waste much time on it if it's not really what's needed.

Below are a couple examples of how it's used - you really have to try it
yourself to see what's generated - I don't want to post tarballs or such on
the list and it's simple to generate and look at the layers.

The first case is just a very simple layer with a layer.conf and README -
basically the simplest layer you can create, and which exists mainly because
even that is easy to get wrong. As with the yocto-bsp tool, the script
queries the user for a couple items, here we just take the defaults, which
are a priority of 6 for the layer and no other components such as example
recipes:

[trz@empanada build]$ yocto-layer create simplestlayer
Please enter the layer priority you'd like to use for the layer: [default: 6]
Would you like to have an example recipe created? (y/n) [default: n]
Would you like to have an example bbappend file created? (y/n) [default: n]

Can these options be specified on the cli? It would be nice for
documentation to not have to list all the questions to describe how to
accomplish a specific task such as this. e.g.

[trz@empanada build]$ yocto-layer create simplestlayer -p 6 --no-recipe
--no-bbappend

Or possibly having defaults to those questions accepted by default
unless [-i|--interactive] is specified?

empanada :-) Mmmmmm


New layer created in meta-simplestlayer.

Don't forget to add it to your BBLAYERS (for details see meta-simplestlayer\README).

[trz@empanada build]$ find .
.
./meta-simplestlayer
./meta-simplestlayer/conf
./meta-simplestlayer/conf/layer.conf
./meta-simplestlayer/README
./meta-simplestlayer/COPYING.MIT

It might make sense to create a recipes/ directory as well, just to
support convention.



In the second case, we tell the tool that we do want an example .bb and and
an example .bbappend. We're queried for the recipe name that we want our
recipe to have, and for the .bbappend, the name of the base recipe and its
version. Below you can see the files it generates - please look at the files
themselves to see the contents. For the recipe example, it generates a recipe
based on the example in the Yocto manual, and my own helloworld.c code
(untested so far which is also why this is an RFC). For the .bbappend example,
it just creates an empty .patch file with some instructions on what to do to
modify the parent recipe with a patch:

[trz@empanada build]$ yocto-layer create mylayer
Please enter the layer priority you'd like to use for the layer: [default: 6]
Would you like to have an example recipe created? (y/n) [default: n] y
Please enter the name you'd like to use for your example recipe: [default: example] flork
Would you like to have an example bbappend file created? (y/n) [default: n] y
Please enter the name you'd like to use for your bbappend file: [default: example] chork
Please enter the version number you'd like to use for your bbappend file (this should match the recipe you're appending to): [default: 0.1] 0.22.3

Wow, that's quite a bit more than I was asking for... I can imagine that
some folks my find that useful.



New layer created in meta-mylayer.

Don't forget to add it to your BBLAYERS (for details see meta-mylayer\README).

[trz@empanada build]$ find .
.
./meta-mylayer
./meta-mylayer/recipes-example
./meta-mylayer/recipes-example/example
./meta-mylayer/recipes-example/example/flork-0.1
./meta-mylayer/recipes-example/example/flork-0.1/helloworld.c
./meta-mylayer/recipes-example/example/flork-0.1/example.patch
./meta-mylayer/recipes-example/example/flork_0.1.bb
./meta-mylayer/conf
./meta-mylayer/conf/layer.conf
./meta-mylayer/recipes-example-bbappend
./meta-mylayer/recipes-example-bbappend/example-bbappend
./meta-mylayer/recipes-example-bbappend/example-bbappend/chork-0.22.3
./meta-mylayer/recipes-example-bbappend/example-bbappend/chork-0.22.3/example.patch
./meta-mylayer/recipes-example-bbappend/example-bbappend/chork_0.22.3.bbappend
./meta-mylayer/README
./meta-mylayer/COPYING.MIT

Please try it and look at the generated code - any comments or suggestions
are welcome.

In concept, looks pretty good to me, and a natural refactoring of
yocto-bsp. I'll review the patches independently.

Thanks,

Darren


Thanks,

Tom

The following changes since commit da598d4f0fcf6faa62055084a51d70d735399d33:

eglibc: fix checksums of fetched patches (2012-12-13 18:02:21 +0000)

are available in the git repository at:

git://git.yoctoproject.org/poky-contrib.git tzanussi/yocto-layer-rfc
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=tzanussi/yocto-layer-rfc

Tom Zanussi (5):
scripts/lib/bsp/engine.py: add yocto_layer_create()
yocto-layer: new script
yocto-layer: add help/usage
yocto-layer: add 'layer' template data
scripts/lib/bsp/engine.py: refactor bsp-creation code

scripts/lib/bsp/engine.py | 86 +++++++-
scripts/lib/bsp/help.py | 228 +++++++++++++++++++++
.../bsp/substrate/target/arch/layer/COPYING.MIT | 17 ++
scripts/lib/bsp/substrate/target/arch/layer/README | 64 ++++++
.../substrate/target/arch/layer/conf/layer.conf | 10 +
.../target/arch/layer/layer-questions.noinstall | 14 ++
.../example.patch" | 12 ++
..._name}}_{{=example_bbappend_version}}.bbappend" | 8 +
.../{{=example_recipe_name}}-0.1/example.patch" | 12 ++
.../{{=example_recipe_name}}-0.1/helloworld.c" | 6 +
.../example/{{=example_recipe_name}}_0.1.bb" | 23 +++
scripts/yocto-layer | 142 +++++++++++++
12 files changed, 612 insertions(+), 10 deletions(-)
create mode 100644 scripts/lib/bsp/substrate/target/arch/layer/COPYING.MIT
create mode 100644 scripts/lib/bsp/substrate/target/arch/layer/README
create mode 100644 scripts/lib/bsp/substrate/target/arch/layer/conf/layer.conf
create mode 100644 scripts/lib/bsp/substrate/target/arch/layer/layer-questions.noinstall
create mode 100644 "scripts/lib/bsp/substrate/target/arch/layer/{{ if create_example_bbappend == \"y\": }} recipes-example-bbappend/example-bbappend/{{=example_bbappend_name}}-{{=example_bbappend_version}}/example.patch"
create mode 100644 "scripts/lib/bsp/substrate/target/arch/layer/{{ if create_example_bbappend == \"y\": }} recipes-example-bbappend/example-bbappend/{{=example_bbappend_name}}_{{=example_bbappend_version}}.bbappend"
create mode 100644 "scripts/lib/bsp/substrate/target/arch/layer/{{ if create_example_recipe == \"y\": }} recipes-example/example/{{=example_recipe_name}}-0.1/example.patch"
create mode 100644 "scripts/lib/bsp/substrate/target/arch/layer/{{ if create_example_recipe == \"y\": }} recipes-example/example/{{=example_recipe_name}}-0.1/helloworld.c"
create mode 100644 "scripts/lib/bsp/substrate/target/arch/layer/{{ if create_example_recipe == \"y\": }} recipes-example/example/{{=example_recipe_name}}_0.1.bb"
create mode 100755 scripts/yocto-layer
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel


Canceled: Yocto Project Technical Team Meeting - Cancelled this week due to holidays

Liu, Song <song.liu@...>
 

When: Tuesday, December 25, 2012 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada).
Where: Bridge Info Enclosed
 
Note: The GMT offset above does not reflect daylight saving time adjustments.
 
*~*~*~*~*~*~*~*~*~*
 
We encourage people attending the meeting to logon the Yocto IRC chancel during the meeting (optional):
 
 
Conference details
Conference name: Yocto Technical Team
Conference date/start time: Tue Jun 26, 2012 at 10:00 AM Central Daylight Time
Participants: 30
Duration: 60 minutes
Participant passcode: 76994298
Dial-in number: 1.972.995.7777
US Toll Free number: 1.877.561.6828
BlackBerry users, click this link to join your conference as a participant: 1.972.995.7777x76994298#
  Depending on where you are dialing from, either your BlackBerry will pause and enter the passcode automatically or you will be prompted to click again to dial the passcode.
Local and Global Access Numbers
 
Country Dial-in number
Australia: 1800 636 843
Czech Republic: 242 430 350
China (Beijing): From office dial 8-9957777 or 8784277
Beijing Out of Office dial 5878 4277
China (Shanghai): From office dial 8-9957777 or 3073322
Shanghai Out of Office dial 2307 3322
China (Shenzen): From office dial 8-9957777 or 6007877
Shenzen Out of Office dial 2600 7877
China (Other Cities): From IP phone dial 8-9957777
Other cities - Non IP phone dial 021-23073322
Denmark: 8060 1400
Finland: 09 41333477
France: 0497 275888
Germany: 08161 803232
Holland: 030 2417490
India: BSNL subscribers use 1800 425 9996 (Toll Free)
Airtel subscribers use 0008 009 861 212 (Toll Free)
From TI Campus use 89957777
Others use 2509 9555 (Landline within Bangalore) or
80 2509 9555 (Outside Bangalore)
Israel: 09 790 6715
Italy: 039 69061234 (039 is local city code not country code)
Japan: From TI Campus use 8 995 7777
Outside TI use 03 4331 3777
Malaysia: From IP phone dial 2643799
From Kuala Lumpur dial 4264 3799
Outside Kuala Lumpur dial (03)4264 3799
Norway: 2 295 8744
Philippines: From Baguio City use 4471177
From Metro Manila area use 8702477
Singapore: From IP phone dial 3894777
Outside TI use 6389 4777
South Korea: From IP phone dial 5606998
From Seoul dial 5606998
Outside Seoul dial (02)5606998
Sweden: 08 58755577
Taiwan: From IP phone dial 1363
From Taipei dial 2241 1363
Outside Taipei dial (02)2241 1363
Turkey: Landline Only dial 0811 288 0001
then enter 877 633 1123
UK: 01604 663003
US: 972 995 7777 or 1877 561 6828
 
Recurring conferences
First scheduled conference: Tue Jun 26, 2012
Recurrence frequency: Weekly - Every 1 week(s) on Tuesday
Recurrence ends: End on Fri Jun 21, 2013, 10:40 AM CDT
 
 
 
 


Weekly build availability.

Flanagan, Elizabeth <elizabeth.flanagan@...>
 

The weekly build will be available in a few hours at:

http://autobuilder.yoctoproject.org/pub/nightly/20121219-5

One known issue is that the eclipse plugin needs to be built alone and
moved manually. I'll do this when it is finished building. This is due
to some autobuilder issues I'll be fixing tonight.

I *will* be producing weekly builds over the holidays in case we have
anyone who wants them.

-b

--
Elizabeth Flanagan
Yocto Project
Build and Release


Re: Git tag systematics ?

Wolfgang Denk <wd@...>
 

Dear Elizabeth,

In message <CAPhnLPBXsYcNDeKsW6xBLjSrJunHUDtkRohR_aHtU9PysQMLhg@...> you wrote:

However, there is no such release tag as "danny-8.0".
You are correct. That was an oversight on my part. I've corrected it.
Thanks.

Is there some formal procedure in place how git release tags are
assigned, and when?

What is the system in this numbering / tagging?
Milestones: 1.x_My.rcz
Major releases: 1.x and they should also get the name-x.y.z tag
Thanks again - but is there any documetn somehere on the web pages or
in the wiki that actually says what the name of the next release will
be, and which branch it is being worked on?

Releated: is there any document which explains the branch names being
used for development. for example, how can I find out ("officially")
what the branch name for Yocto 1.4 will be / is ?
When Richard tells me :)
We have a "1.4_M1.final" tag in the "1.4_M1" branch, and I see similar
"1.x_My" branches for the other releases. When will some "name-..."
branch become visible?

Best regards,

Wolfgang Denk

--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@...
Lots of people drink from the wrong bottle sometimes.
-- Edith Keeler, "The City on the Edge of Forever",
stardate unknown


Re: How to use JRE (Java Runtime) in Yocto Projects

Paul Eggleton
 

On Wednesday 19 December 2012 15:31:42 Raul Rosetto Munoz wrote:
raul@phi04:/home/prjs/poky$ git branch
* local/origin/denzil
There doesn't seem to be a denzil branch for meta-java and it's likely the
error you're receiving is because the master branch of meta-java is
incompatible with the denzil release. I would suggest updating to the danny
release, or alternatively you'll need to modify meta-java to be compatible
with denzil (i.e. you'll have to match indenting in python functions such as
populate_packages_prepend).

Cheers,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre


Re: How to use JRE (Java Runtime) in Yocto Projects

Raul Mu?oz
 

raul@phi04:/home/prjs/poky$ git branch 
* local/origin/denzil



2012/12/19 Raul Rosetto Munoz <munoz0raul@...>

raul@phi04:/home/prjs/newcom0001/workspace/philinux/philinux-imx28-newcom$ bitbake --version
BitBake Build Tool Core version 1.15.2, bitbake version 1.15.2



2012/12/19 Paul Eggleton <paul.eggleton@...>
On Wednesday 19 December 2012 08:25:00 Raul Rosetto Munoz wrote:
> Hello all,
> I did some things like this wiki.
>
> I added the meta-java layer but the only important diference is that I'm
> using meta poky (/poky/meta) and no meta oe-core (/oe-core/meta).
>
> https://github.com/woglinde/meta-java/wiki
>
> The fisrt probleme tha I have is that the package LLVM show me some errors.
>
> here is what I have:
>
> raul@phi04:/home/prjs/newcom0001/workspace/philinux/philinux-imx28-newcom$
> bitbake openjdk-6
> WARNING: Host distribution "Ubuntu 12.04.1 LTS" has not been validated with
> this version of the build system; you may possibly experience unexpected
> failures. It is recommended that you use a tested distribution.
> NOTE: Error expanding variable populate_packages
>
>                                                             | ETA:  00:00:38
>
> NOTE: Error during finalise of
> /home/prjs/newcom0001/workspace/philinux/meta-java/recipes-core/llvm/
> llvm2.8_2.8.bb
> ERROR: Unable to parse
> /home/prjs/newcom0001/workspace/philinux/meta-java/recipes-core/llvm/
> llvm2.8_2.8.bb
> ERROR: Command execution failed: Traceback (most recent call last):
>   File "/home/prjs/poky/bitbake/lib/bb/command.py", line 84, in
> runAsyncCommand
>     self.cooker.updateCache()
>   File "/home/prjs/poky/bitbake/lib/bb/cooker.py", line 1202, in updateCache
> if not self.parser.parse_next():
>   File "/home/prjs/poky/bitbake/lib/bb/cooker.py", line 1669, in parse_next
>     self.virtuals += len(result)
> UnboundLocalError: local variable 'result' referenced before assignment
>
>
> Summary: There was 1 WARNING message shown.
> Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
> raul@phi04:/home/prjs/newcom0001/workspace/philinux/philinux-imx28-newcom$

Which version of the build system are you using?

Cheers,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre



--
Raul Rosetto Muñoz



--
Raul Rosetto Muñoz


Re: How to use JRE (Java Runtime) in Yocto Projects

Raul Mu?oz
 

raul@phi04:/home/prjs/newcom0001/workspace/philinux/philinux-imx28-newcom$ bitbake --version
BitBake Build Tool Core version 1.15.2, bitbake version 1.15.2



2012/12/19 Paul Eggleton <paul.eggleton@...>

On Wednesday 19 December 2012 08:25:00 Raul Rosetto Munoz wrote:
> Hello all,
> I did some things like this wiki.
>
> I added the meta-java layer but the only important diference is that I'm
> using meta poky (/poky/meta) and no meta oe-core (/oe-core/meta).
>
> https://github.com/woglinde/meta-java/wiki
>
> The fisrt probleme tha I have is that the package LLVM show me some errors.
>
> here is what I have:
>
> raul@phi04:/home/prjs/newcom0001/workspace/philinux/philinux-imx28-newcom$
> bitbake openjdk-6
> WARNING: Host distribution "Ubuntu 12.04.1 LTS" has not been validated with
> this version of the build system; you may possibly experience unexpected
> failures. It is recommended that you use a tested distribution.
> NOTE: Error expanding variable populate_packages
>
>                                                             | ETA:  00:00:38
>
> NOTE: Error during finalise of
> /home/prjs/newcom0001/workspace/philinux/meta-java/recipes-core/llvm/
> llvm2.8_2.8.bb
> ERROR: Unable to parse
> /home/prjs/newcom0001/workspace/philinux/meta-java/recipes-core/llvm/
> llvm2.8_2.8.bb
> ERROR: Command execution failed: Traceback (most recent call last):
>   File "/home/prjs/poky/bitbake/lib/bb/command.py", line 84, in
> runAsyncCommand
>     self.cooker.updateCache()
>   File "/home/prjs/poky/bitbake/lib/bb/cooker.py", line 1202, in updateCache
> if not self.parser.parse_next():
>   File "/home/prjs/poky/bitbake/lib/bb/cooker.py", line 1669, in parse_next
>     self.virtuals += len(result)
> UnboundLocalError: local variable 'result' referenced before assignment
>
>
> Summary: There was 1 WARNING message shown.
> Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
> raul@phi04:/home/prjs/newcom0001/workspace/philinux/philinux-imx28-newcom$

Which version of the build system are you using?

Cheers,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre



--
Raul Rosetto Muñoz


Re: How to use JRE (Java Runtime) in Yocto Projects

Paul Eggleton
 

On Wednesday 19 December 2012 08:25:00 Raul Rosetto Munoz wrote:
Hello all,
I did some things like this wiki.

I added the meta-java layer but the only important diference is that I'm
using meta poky (/poky/meta) and no meta oe-core (/oe-core/meta).

https://github.com/woglinde/meta-java/wiki

The fisrt probleme tha I have is that the package LLVM show me some errors.

here is what I have:

raul@phi04:/home/prjs/newcom0001/workspace/philinux/philinux-imx28-newcom$
bitbake openjdk-6
WARNING: Host distribution "Ubuntu 12.04.1 LTS" has not been validated with
this version of the build system; you may possibly experience unexpected
failures. It is recommended that you use a tested distribution.
NOTE: Error expanding variable populate_packages

| ETA: 00:00:38

NOTE: Error during finalise of
/home/prjs/newcom0001/workspace/philinux/meta-java/recipes-core/llvm/
llvm2.8_2.8.bb
ERROR: Unable to parse
/home/prjs/newcom0001/workspace/philinux/meta-java/recipes-core/llvm/
llvm2.8_2.8.bb
ERROR: Command execution failed: Traceback (most recent call last):
File "/home/prjs/poky/bitbake/lib/bb/command.py", line 84, in
runAsyncCommand
self.cooker.updateCache()
File "/home/prjs/poky/bitbake/lib/bb/cooker.py", line 1202, in updateCache
if not self.parser.parse_next():
File "/home/prjs/poky/bitbake/lib/bb/cooker.py", line 1669, in parse_next
self.virtuals += len(result)
UnboundLocalError: local variable 'result' referenced before assignment


Summary: There was 1 WARNING message shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
raul@phi04:/home/prjs/newcom0001/workspace/philinux/philinux-imx28-newcom$
Which version of the build system are you using?

Cheers,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre


Re: How to use JRE (Java Runtime) in Yocto Projects

Raul Mu?oz
 

Hello all,
I did some things like this wiki.

I added the meta-java layer but the only important diference is that I'm using meta poky (/poky/meta) and no meta oe-core (/oe-core/meta).


The fisrt probleme tha I have is that the package LLVM show me some errors.

here is what I have:

raul@phi04:/home/prjs/newcom0001/workspace/philinux/philinux-imx28-newcom$ bitbake openjdk-6
WARNING: Host distribution "Ubuntu 12.04.1 LTS" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution.
NOTE: Error expanding variable populate_packages                                                                                       | ETA:  00:00:38
NOTE: Error during finalise of /home/prjs/newcom0001/workspace/philinux/meta-java/recipes-core/llvm/llvm2.8_2.8.bb
ERROR: Unable to parse /home/prjs/newcom0001/workspace/philinux/meta-java/recipes-core/llvm/llvm2.8_2.8.bb
ERROR: Command execution failed: Traceback (most recent call last):
  File "/home/prjs/poky/bitbake/lib/bb/command.py", line 84, in runAsyncCommand
    self.cooker.updateCache()
  File "/home/prjs/poky/bitbake/lib/bb/cooker.py", line 1202, in updateCache
    if not self.parser.parse_next():
  File "/home/prjs/poky/bitbake/lib/bb/cooker.py", line 1669, in parse_next
    self.virtuals += len(result)
UnboundLocalError: local variable 'result' referenced before assignment


Summary: There was 1 WARNING message shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
raul@phi04:/home/prjs/newcom0001/workspace/philinux/philinux-imx28-newcom$ 


Thanks


FW: Fullpass Test Report for Yocto 1.2.2 denzil-next 20121206 Build

Palalau, AlexandruX <alexandrux.palalau@...>
 

 

Somehow, this didn’t get sent last night…

Br,

--

Alexandru Palalau

QA Contractor @ Yocto Project

Open-source Technology Center Romania

System Software Division

 

From: Palalau, AlexandruX

Sent: Tuesday, December 18, 2012 11:17 PM
To: yocto@...
Cc: Liu, Song
Subject: Fullpass Test Report for Yocto 1.2.2 denzil-next 20121206 Build

 

Hello,


Here is the Fullpass Test Report for Yocto 1.2.2 denzil-next 20121206 build.

There are some issues regarding the following:

è CoreBuildSystem: libowl fetch and build appliance build fail

è HOB: toolchain settings are not saved and trying to build a recipe from terminal using HOB conf fails

è Jasperforest: syslog fails(fixed in master) and and also the iptables compilation is failing for this architecture.

è Atom-PC: failure in starting the installed instance. Also, return from standby fails and we have some dmesg errors.

 

Attached you can find the full test report.

Test Summary
-------------------------

Test Result Summary

Component

Target

Status

Comments

QEMU

qemux86

GOOD

Everything runs well

 

qemux86-64

GOOD

Everything runs well

BSP

e-Menlow

GOOD

No USB notification

 

Hurronriver

GOOD

Everything runs well

 

Jasperforest

BUGGY

Syslog fails
iptables project compilation fail

 

Atom-PC

BUGGY

Install from USB fails
Cannot return from standby

Core Build System

BUGGY

libowl do_fetch fails
Build Appliance fails to build due to build_boot_dd

ADT Toolchain

GOOD

Everything runs well

HOB

 

BUGGY

toolchain arch in settings is not saved
Hob recipe build from terminal fails

 

BLOCK

Critical bugs, more than 50% test cases are blocked

GOOD

Only Normal, Minor or Enhancement bugs, less than 10% test cases failed

BUGGY

Normal, Major and Critical bugs, more than 10% test cases failed

 

Detailed Test Result for each component

Target

Total TCs

Not Run

Passed

Failed

Not testable (Blocked)

Qemux86 Sato-SDK

37

0

37

0

0

Qemux86-64 Sato-SDK

37

0

37

0

0

Core Build System

48

6

36

6(2821,3339)

6

ADT Toolchain

53

2

51

0

2

HOB

38

0

36

2(2695,3001)

0

Stress

2

0

2

0

0

Compliance

2

0

2

0

0

Distro

14

0

14

0

0

e-Menlow

66

0

65

1(2643)

0

Hurronriver

68

0

68

0

0

Jasperforest

35

0

    32

3(3618,2053)

0

Atom-PC

66

3

     60

3(3591,3588,3590)

3

Total

466

11

440

15

11


* You can check the detailed test result in attachment for each target.
** The failed/blocked case number is listed with failed cases’ bug number.


Commit information
--------------------------------

Location: http://autobuilder.pokylinux.org/nightly/20121206-1/
Tree/Branch: sgarman/denzil-next-pull4
Commit: d166ea7bb13eaf25b54e14f0bf9c5747ea950617
Issue Summary
-----------------------------------

Component

Bug Number

Target Milestone

Core Build System

Bug 2821 - libowl do_fetch error
Bug 3339 - Build Appliance fails to build

1.4 M1
1.2.2

HOB

Bug 2695 - [HOB]toolchain arch in settings is not saved
Bug 3001 – Hob recipe build from terminal fails

1.3 M4
---

Jasperforest

New! Bug 3618 syslog fails
Bug 2053 - iptables-1.4.12.2-r0: task do_compile

---
1.2 M4

Atom-PC

Bug 3591 - [ATOM-PC] cannot boot after install - stops at grub
Bug 3590 - [Atom-PC]Return from standby fails
Bug 3588 - [Atom-PC]dmesg errors

---
---
---

 

Best Regards,


--

Alexandru Palalau

QA Contractor @ Yocto Project

Open-source Technology Center Romania

System Software Division

 

 


Fullpass Test Report for Yocto 1.2.2 denzil-next 20121206 Build

Palalau, AlexandruX <alexandrux.palalau@...>
 

Hello,


Here is the Fullpass Test Report for Yocto 1.2.2 denzil-next 20121206 build.

There are some issues regarding the following:

è CoreBuildSystem: libowl fetch and build appliance build fail

è HOB: toolchain settings are not saved and trying to build a recipe from terminal using HOB conf fails

è Jasperforest: syslog fails(fixed in master) and and also the iptables compilation is failing for this architecture.

è Atom-PC: failure in starting the installed instance. Also, return from standby fails and we have some dmesg errors.

 

Attached you can find the full test report.

Test Summary
-------------------------

Test Result Summary

Component

Target

Status

Comments

QEMU

qemux86

GOOD

Everything runs well

 

qemux86-64

GOOD

Everything runs well

BSP

e-Menlow

GOOD

No USB notification

 

Hurronriver

GOOD

Everything runs well

 

Jasperforest

BUGGY

Syslog fails
iptables project compilation fail

 

Atom-PC

BUGGY

Install from USB fails
Cannot return from standby

Core Build System

BUGGY

libowl do_fetch fails
Build Appliance fails to build due to build_boot_dd

ADT Toolchain

GOOD

Everything runs well

HOB

 

BUGGY

toolchain arch in settings is not saved
Hob recipe build from terminal fails

 

BLOCK

Critical bugs, more than 50% test cases are blocked

GOOD

Only Normal, Minor or Enhancement bugs, less than 10% test cases failed

BUGGY

Normal, Major and Critical bugs, more than 10% test cases failed

 

Detailed Test Result for each component

Target

Total TCs

Not Run

Passed

Failed

Not testable (Blocked)

Qemux86 Sato-SDK

37

0

37

0

0

Qemux86-64 Sato-SDK

37

0

37

0

0

Core Build System

48

6

36

6(2821,3339)

6

ADT Toolchain

53

2

51

0

2

HOB

38

0

36

2(2695,3001)

0

Stress

2

0

2

0

0

Compliance

2

0

2

0

0

Distro

14

0

14

0

0

e-Menlow

66

0

65

1(2643)

0

Hurronriver

68

0

68

0

0

Jasperforest

35

0

    32

3(3618,2053)

0

Atom-PC

66

3

     60

3(3591,3588,3590)

3

Total

466

11

440

15

11


* You can check the detailed test result in attachment for each target.
** The failed/blocked case number is listed with failed cases’ bug number.


Commit information
--------------------------------

Location: http://autobuilder.pokylinux.org/nightly/20121206-1/
Tree/Branch: sgarman/denzil-next-pull4
Commit: d166ea7bb13eaf25b54e14f0bf9c5747ea950617
Issue Summary
-----------------------------------

Component

Bug Number

Target Milestone

Core Build System

Bug 2821 - libowl do_fetch error
Bug 3339 - Build Appliance fails to build

1.4 M1
1.2.2

HOB

Bug 2695 - [HOB]toolchain arch in settings is not saved
Bug 3001 – Hob recipe build from terminal fails

1.3 M4
---

Jasperforest

New! Bug 3618 syslog fails
Bug 2053 - iptables-1.4.12.2-r0: task do_compile

---
1.2 M4

Atom-PC

Bug 3591 - [ATOM-PC] cannot boot after install - stops at grub
Bug 3590 - [Atom-PC]Return from standby fails
Bug 3588 - [Atom-PC]dmesg errors

---
---
---

 

Best Regards,


--

Alexandru Palalau

QA Contractor @ Yocto Project

Open-source Technology Center Romania

System Software Division