Re: [yocto] [question] icecc: improve interaction with sstate
On Sat, Mar 16, 2013 at 5:38 PM, Burton, Ross ross.bur...@intel.com wrote: On 16 March 2013 01:16, Insop Song insop.s...@gmail.com wrote: So at this point, I will wait to see if any one is seen this recently. The autobuilder appears to be hitting this still, but as several oe-core maintainers are still travelling after a conference you may have to wait until Monday. Thank you for the update while you are on the road. I pull the latest again (http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=2381e46e77c8d33472f60861f66e44addd53af68) And it is okay now. Could be the Richard's this commit fixed it. package_rpm: Ensure PV manipulations are correct Richard Purdie (b5e5d25c25f30db1f9855e24afef9d8f0bb77d35) Here is my output: --- ~/mybuilds/meta-realtime $ time bitbake core-image-realtime Loading cache: 100% |##| ETA: 00:00:00 Loaded 1123 entries from dependency cache. Build Configuration: BB_VERSION= 1.17.1 BUILD_SYS = i686-linux NATIVELSBSTRING = Ubuntu-12.10 TARGET_SYS= i586-poky-linux MACHINE = qemux86 DISTRO= poky DISTRO_VERSION= 1.3+snapshot-20130316 TUNE_FEATURES = m32 i586 TARGET_FPU= meta meta-yocto meta-yocto-bsp= master:2381e46e77c8d33472f60861f66e44addd53af68 meta-realtime = schedtool-sq:ed7886f649ab945625ccbfed0ecc74a500a7c22d NOTE: Resolving any missing task queue dependencies NOTE: Preparing runqueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks NOTE: Tasks Summary: Attempted 3938 tasks of which 2355 didn't need to be rerun and all succeeded. real122m1.472s user514m20.641s sys 73m56.453s -- regards, Insop ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 1/1] add scheedtool-dl for testing sched_deadline use jiri's github as a main repo
On Sat, Mar 16, 2013 at 10:01 PM, Khem Raj raj.k...@gmail.com wrote:
On Mar 15, 2013, at 4:47 AM, Insop Song insop.s...@gmail.com wrote:
+SRCREV = ${AUTOREV}
IMO find a good revision and send that one here. you can use AUTOREV
internally for your
development thats all fine
Hi Khem,
Thank you for the review.
I've updated that already as Bruce suggested the same as well in the
latest patch update.
Here is the update patch for your reference.
Thank you.
Insop
+From 041b2b65889c44c47f90313c5bf9ce61effa96df Mon Sep 17 00:00:00 2001
+From: Insop Song insop.s...@gmail.com
+Date: Sat, 9 Mar 2013 01:23:24 -0800
+Subject: [PATCH] set --with-deadline as a default to go around yocto build
+ error on deadline enabled
+
+---
+ configure.ac |2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/configure.ac b/configure.ac
+index a5e2990..64e57e4 100644
+--- a/configure.ac
b/configure.ac
+@@ -34,7 +34,7 @@ AC_ARG_WITH([deadline],
+ [AS_HELP_STRING([--with-deadline],
+ [Add support for SCHED_DEADLINE])],
+ [],
+- [with_deadline=no])
++ [with_deadline=yes])
+
+ AS_IF([test x$with_deadline != xno],
+ [AC_DEFINE([DLSCHED], [1], [Define if you have SCHED_DEADLINE support])
+--
+1.7.9.5
+
diff --git a/recipes-tools/rt-app/rt-app.bb b/recipes-tools/rt-app/rt-app.bb
new file mode 100644
index 000..acce437
--- /dev/null
+++ b/recipes-tools/rt-app/rt-app.bb
@@ -0,0 +1,28 @@
+DESCRIPTION = rt-app is a test application that starts multiple
periodic threads in order to simulate a real-time periodic load
+SECTION = devel
+LICENSE = GPLv2
+LIC_FILES_CHKSUM =
file://COPYING;endline=339;md5=e43fc16fccd8519fba405f0a0ff6e8a3
+PR = r1
+
+SRCREV = e81cbe9f76ee298feded17bb7455d4deb2fb32af
+
+SRC_URI = git://github.com/gbagnoli/rt-app.git \
+ file://0001-set-with-deadline-as-a-default-to-go-around-yocto-bu.patch \
+
+
+S = ${WORKDIR}/git
+
+inherit autotools gettext pkgconfig
+
+do_configure_prepend() {
+ autoreconf --install --verbose --force
+}
+
+do_install() {
+ install -d ${D}${bindir}
+ install -m 0755 src/rt-app ${D}${bindir}
+}
+
+FILES_{PN} = ${bindir}/rt-app
+
+PARALLEL_MAKE =
diff --git a/recipes-tools/schedtool-dl/schedtool-dl.bb
b/recipes-tools/schedtool-dl/schedtool-dl.bb
new file mode 100644
index 000..5592175
--- /dev/null
+++ b/recipes-tools/schedtool-dl/schedtool-dl.bb
@@ -0,0 +1,23 @@
+DESCRIPTION = schedtool-dl (scheduler test tool) for deadline scheduler
+SECTION = devel
+LICENSE = GPLv2
+LIC_FILES_CHKSUM =
file://Makefile;endline=55;md5=e4b4e8ed9c2132e1d727a1bb5e3bd984
+PR = r1
+
+SRC_URI = git://github.com/jlelli/schedtool-dl.git;protocol=git
+SRCREV = cd4e3f2f5a33c3266e25e447e8efbacb3b8c88da
+
+S = ${WORKDIR}/git
+
+do_compile() {
+ oe_runmake
+}
+
+do_install() {
+ install -d ${D}${bindir}
+ install -m 0755 schedtool ${D}${bindir}
+}
+
+FILES_{PN} = ${bindir}/schedtool
+
+PARALLEL_MAKE =
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [linux-yocto] [PATCH 0/1] [meta-realtime] Add rt-app, schedtool, define core-image-realtime, and append recipies-kernel
On Sat, Mar 16, 2013 at 9:04 PM, Bruce Ashfield bruce.ashfi...@windriver.com wrote: This looks good to me now, I still think we'll have some confusion between the core rt images and core-image-realtime that we are introducing here. I may rename it core-image-realtime-extended as part of the merge, if that's acceptable to you ? I think it will be something that we'll need to revisit at some point, but that's not a good reason to hold this back anymore. I'll merge, do a quick test and push this out on Monday. core-image-realtime-extended or core-image-rt-extended (to be aligned with existing core-image-rt) or something along this line sounds fine to me. I was thinking of updating my patch, but it would be better if you decide the final name, so I won't update the patch for now. Or if you know which name is the best, then just let me know, I will update the patch and send it to you. Thank you, Insop ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] distribution validation
On Mar 15, 2013, at 5:02 AM, Trevor Woerner twoer...@gmail.com wrote: A new version of openSuSE has been released. What's the criteria for determining that a given version of a distribution has been validated for Yocto? What is required in order to add it to the list of valid distirbutions? I would say for all machines in OE-Core if bitbake world works then its pretty good ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] burn images to usb problem!!!
Hello Florin, In the poky folder there is a README.hardware file which contain instructions on how to write an image to the USB drive. Here is a section of that file: USB Device: 1. Build a live image. This image type consists of a simple filesystem without a partition table, which is suitable for USB keys, and with the default setup for the atom-pc machine, this image type is built automatically for any image you build. For example: $ bitbake core-image-minimal 2. Use the dd utility to write the image to the raw block device. For example: # dd if=core-image-minimal-atom-pc.hddimg of=/dev/sdb Please make sure you read all the additional information you may need to understand the steps in building an image for a particular device. We are glad to have you onboard in the Embedded Linux community. Regards, -- Alexandru Georgescu Yocto QA Engineer From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Florin Cristian Dan Sent: Sunday, March 17, 2013 01:38 To: yocto@yoctoproject.org Subject: [yocto] burn images to usb problem!!! hello, I'm preety new with linux embedded and especially with Yocyo Project wich by the way i think it's awesome. I managed to build a core-image-sato-quemux86, it runs ok within qemu, but now i want to boot this image from a USB memory stick, and i don't know how to do it, and wich files from /build/tmp/deploy/images to use. I will be greatefull, for an answer, thank you very much ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] problems building 'neard'
I'm not sure if this is specific to my host, but: Build Configuration: BB_VERSION= 1.17.1 BUILD_SYS = x86_64-linux NATIVELSBSTRING = openSUSE-project-12.3 TARGET_SYS= i586-poky-linux MACHINE = qemux86 DISTRO= poky DISTRO_VERSION= 1.3+snapshot-20130317 TUNE_FEATURES = m32 i586 TARGET_FPU= meta meta-yocto meta-yocto-bsp= master:1ceb13dda11645229053fc4840954333f8910ba4 ERROR: Function failed: BUILDSPEC (see /home/trevor/devel/yocto/git-method/coreimgmin/tmp/work/i586-poky-linux/neard/0.9-gitAUTOINC+1e20e396cb837017b7e5ef822bfdab6ce060d2cf-r1/temp/log.do_package_write_rpm.15728 for further information) ERROR: Logfile of failure stored in: /home/trevor/devel/yocto/git-method/coreimgmin/tmp/work/i586-poky-linux/neard/0.9-gitAUTOINC+1e20e396cb837017b7e5ef822bfdab6ce060d2cf-r1/temp/log.do_package_write_rpm.15728 Log data follows: | DEBUG: Executing python function sstate_task_prefunc | DEBUG: Python function sstate_task_prefunc finished | DEBUG: Executing python function do_package_write_rpm | DEBUG: Executing python function read_subpackage_metadata | DEBUG: Python function read_subpackage_metadata finished | DEBUG: Executing python function do_package_rpm | DEBUG: Executing python function write_specfile | NOTE: Not creating empty RPM package for neard-tests | NOTE: Creating RPM package for neard-dbg | NOTE: Not creating empty RPM package for neard-staticdev | NOTE: Creating RPM package for neard-dev | NOTE: Not creating empty RPM package for neard-doc | NOTE: Not creating empty RPM package for neard-locale | NOTE: Creating RPM package for neard | NOTE: Creating RPM package for neard | DEBUG: Python function write_specfile finished | DEBUG: SITE files ['endian-little', 'bit-32', 'ix86-common', 'common-linux', 'common-glibc', 'i586-linux', 'common'] | DEBUG: Executing shell function BUILDSPEC | error: line 152: Illegal char '-' in EVR: Suggests: neard = 0.9-git0+1e20e396cb837017b7e5ef822bfdab6ce060d2cf-r1 | error: Package has no %description: neard-dbg.i586 | Building target platforms: i586-poky-linux | DEBUG: Python function do_package_rpm finished | DEBUG: Python function do_package_write_rpm finished | ERROR: Function failed: BUILDSPEC (see /home/trevor/devel/yocto/git-method/coreimgmin/tmp/work/i586-poky-linux/neard/0.9-gitAUTOINC+1e20e396cb837017b7e5ef822bfdab6ce060d2cf-r1/temp/log.do_package_write_rpm.15728 for further information) ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] problems building 'neard'
Update your oe-core to include http://git.openembedded.org/openembedded-core/commit/?id=0f8447a7d99d2645b932eac1c24149f0c2d3791e On Sun, Mar 17, 2013 at 10:37 PM, Trevor Woerner twoer...@gmail.com wrote: I'm not sure if this is specific to my host, but: Build Configuration: BB_VERSION= 1.17.1 BUILD_SYS = x86_64-linux NATIVELSBSTRING = openSUSE-project-12.3 TARGET_SYS= i586-poky-linux MACHINE = qemux86 DISTRO= poky DISTRO_VERSION= 1.3+snapshot-20130317 TUNE_FEATURES = m32 i586 TARGET_FPU= meta meta-yocto meta-yocto-bsp= master:1ceb13dda11645229053fc4840954333f8910ba4 ERROR: Function failed: BUILDSPEC (see /home/trevor/devel/yocto/git-method/coreimgmin/tmp/work/i586-poky-linux/neard/0.9-gitAUTOINC+1e20e396cb837017b7e5ef822bfdab6ce060d2cf-r1/temp/log.do_package_write_rpm.15728 for further information) ERROR: Logfile of failure stored in: /home/trevor/devel/yocto/git-method/coreimgmin/tmp/work/i586-poky-linux/neard/0.9-gitAUTOINC+1e20e396cb837017b7e5ef822bfdab6ce060d2cf-r1/temp/log.do_package_write_rpm.15728 Log data follows: | DEBUG: Executing python function sstate_task_prefunc | DEBUG: Python function sstate_task_prefunc finished | DEBUG: Executing python function do_package_write_rpm | DEBUG: Executing python function read_subpackage_metadata | DEBUG: Python function read_subpackage_metadata finished | DEBUG: Executing python function do_package_rpm | DEBUG: Executing python function write_specfile | NOTE: Not creating empty RPM package for neard-tests | NOTE: Creating RPM package for neard-dbg | NOTE: Not creating empty RPM package for neard-staticdev | NOTE: Creating RPM package for neard-dev | NOTE: Not creating empty RPM package for neard-doc | NOTE: Not creating empty RPM package for neard-locale | NOTE: Creating RPM package for neard | NOTE: Creating RPM package for neard | DEBUG: Python function write_specfile finished | DEBUG: SITE files ['endian-little', 'bit-32', 'ix86-common', 'common-linux', 'common-glibc', 'i586-linux', 'common'] | DEBUG: Executing shell function BUILDSPEC | error: line 152: Illegal char '-' in EVR: Suggests: neard = 0.9-git0+1e20e396cb837017b7e5ef822bfdab6ce060d2cf-r1 | error: Package has no %description: neard-dbg.i586 | Building target platforms: i586-poky-linux | DEBUG: Python function do_package_rpm finished | DEBUG: Python function do_package_write_rpm finished | ERROR: Function failed: BUILDSPEC (see /home/trevor/devel/yocto/git-method/coreimgmin/tmp/work/i586-poky-linux/neard/0.9-gitAUTOINC+1e20e396cb837017b7e5ef822bfdab6ce060d2cf-r1/temp/log.do_package_write_rpm.15728 for further information) ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] problems building 'neard'
I've also ran into this issue and raised in other mail thread. It seems it is fixed with the latest pull. Here was my mail response for your reference: On Sat, Mar 16, 2013 at 5:38 PM, Burton, Ross ross.bur...@intel.com wrote: On 16 March 2013 01:16, Insop Song insop.s...@gmail.com wrote: So at this point, I will wait to see if any one is seen this recently. The autobuilder appears to be hitting this still, but as several oe-core maintainers are still travelling after a conference you may have to wait until Monday. Thank you for the update while you are on the road. I pull the latest again (http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=2381e46e77c8d33472f60861f66e44addd53af68) And it is okay now. Could be the Richard's this commit fixed it. package_rpm: Ensure PV manipulations are correct Richard Purdie (b5e5d25c25f30db1f9855e24afef9d8f0bb77d35) Here is my output: --- ~/mybuilds/meta-realtime $ time bitbake core-image-realtime Loading cache: 100% |##| ETA: 00:00:00 Loaded 1123 entries from dependency cache. Build Configuration: BB_VERSION= 1.17.1 BUILD_SYS = i686-linux NATIVELSBSTRING = Ubuntu-12.10 TARGET_SYS= i586-poky-linux MACHINE = qemux86 DISTRO= poky DISTRO_VERSION= 1.3+snapshot-20130316 TUNE_FEATURES = m32 i586 TARGET_FPU= meta meta-yocto meta-yocto-bsp= master:2381e46e77c8d33472f60861f66e44addd53af68 meta-realtime = schedtool-sq:ed7886f649ab945625ccbfed0ecc74a500a7c22d NOTE: Resolving any missing task queue dependencies NOTE: Preparing runqueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks NOTE: Tasks Summary: Attempted 3938 tasks of which 2355 didn't need to be rerun and all succeeded. real122m1.472s user514m20.641s sys 73m56.453s -- regards, Insop On Sun, Mar 17, 2013 at 2:44 PM, Martin Jansa martin.ja...@gmail.com wrote: Update your oe-core to include http://git.openembedded.org/openembedded-core/commit/?id=0f8447a7d99d2645b932eac1c24149f0c2d3791e On Sun, Mar 17, 2013 at 10:37 PM, Trevor Woerner twoer...@gmail.com wrote: I'm not sure if this is specific to my host, but: Build Configuration: BB_VERSION= 1.17.1 BUILD_SYS = x86_64-linux NATIVELSBSTRING = openSUSE-project-12.3 TARGET_SYS= i586-poky-linux MACHINE = qemux86 DISTRO= poky DISTRO_VERSION= 1.3+snapshot-20130317 TUNE_FEATURES = m32 i586 TARGET_FPU= meta meta-yocto meta-yocto-bsp= master:1ceb13dda11645229053fc4840954333f8910ba4 ERROR: Function failed: BUILDSPEC (see /home/trevor/devel/yocto/git-method/coreimgmin/tmp/work/i586-poky-linux/neard/0.9-gitAUTOINC+1e20e396cb837017b7e5ef822bfdab6ce060d2cf-r1/temp/log.do_package_write_rpm.15728 for further information) ERROR: Logfile of failure stored in: /home/trevor/devel/yocto/git-method/coreimgmin/tmp/work/i586-poky-linux/neard/0.9-gitAUTOINC+1e20e396cb837017b7e5ef822bfdab6ce060d2cf-r1/temp/log.do_package_write_rpm.15728 Log data follows: | DEBUG: Executing python function sstate_task_prefunc | DEBUG: Python function sstate_task_prefunc finished | DEBUG: Executing python function do_package_write_rpm | DEBUG: Executing python function read_subpackage_metadata | DEBUG: Python function read_subpackage_metadata finished | DEBUG: Executing python function do_package_rpm | DEBUG: Executing python function write_specfile | NOTE: Not creating empty RPM package for neard-tests | NOTE: Creating RPM package for neard-dbg | NOTE: Not creating empty RPM package for neard-staticdev | NOTE: Creating RPM package for neard-dev | NOTE: Not creating empty RPM package for neard-doc | NOTE: Not creating empty RPM package for neard-locale | NOTE: Creating RPM package for neard | NOTE: Creating RPM package for neard | DEBUG: Python function write_specfile finished | DEBUG: SITE files ['endian-little', 'bit-32', 'ix86-common', 'common-linux', 'common-glibc', 'i586-linux', 'common'] | DEBUG: Executing shell function BUILDSPEC | error: line 152: Illegal char '-' in EVR: Suggests: neard = 0.9-git0+1e20e396cb837017b7e5ef822bfdab6ce060d2cf-r1 | error: Package has no %description: neard-dbg.i586 | Building target platforms: i586-poky-linux | DEBUG: Python function do_package_rpm finished | DEBUG: Python function do_package_write_rpm finished | ERROR: Function failed: BUILDSPEC (see /home/trevor/devel/yocto/git-method/coreimgmin/tmp/work/i586-poky-linux/neard/0.9-gitAUTOINC+1e20e396cb837017b7e5ef822bfdab6ce060d2cf-r1/temp/log.do_package_write_rpm.15728 for further information) ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org
Re: [yocto] [question] icecc: improve interaction with sstate
On Fri, Mar 15, 2013 at 10:37:56PM -0700, Insop Song wrote: Hi, I am using HEAD of master, and I have this error after I use commit Please use better Subject next time, I was wondering what could be broken by my patch to icecc and your question is quite unrelated to that commit. Something like neard failing to build with latest poky would be better. commit 1ceb13dda11645229053fc4840954333f8910ba4 Author: Martin Jansa martin.ja...@gmail.com Date: Wed Mar 13 20:04:51 2013 +0100 Could anyone know about this? - my config Build Configuration: BB_VERSION= 1.17.1 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Ubuntu-12.04 TARGET_SYS= i586-poky-linux MACHINE = qemux86 DISTRO= poky DISTRO_VERSION= 1.3+snapshot-20130316 TUNE_FEATURES = m32 i586 TARGET_FPU= meta meta-yocto= master:1ceb13dda11645229053fc4840954333f8910ba4 meta-realtime = schedtool:a766d16a1cf4da3c2dd13b8c7e53f89775733187 meta-yocto-bsp= master:1ceb13dda11645229053fc4840954333f8910ba4 - error output: ERROR: Function failed: BUILDSPEC (see /home/insop/mybuilds/meta-realtime/tmp/work/i586-poky-linux/neard/0.9-gitAUTOINC+1e20e396cb837017b7e5ef822bfdab6ce060d2cf-r1/temp/log.do_package_write_rpm.31563 for further information) ERROR: Logfile of failure stored in: /home/insop/mybuilds/meta-realtime/tmp/work/i586-poky-linux/neard/0.9-gitAUTOINC+1e20e396cb837017b7e5ef822bfdab6ce060d2cf-r1/temp/log.do_package_write_rpm.31563 - full output: ~/mybuilds/meta-realtime $ time bitbake core-image-realtime Loading cache: 100% || ETA: 00:00:00 Loaded 1121 entries from dependency cache. Parsing recipes: 100% |##| Time: 00:00:00 Parsing of 813 .bb files complete (812 cached, 1 parsed). 1121 targets, 27 skipped, 0 masked, 0 errors. Build Configuration: BB_VERSION= 1.17.1 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Ubuntu-12.04 TARGET_SYS= i586-poky-linux MACHINE = qemux86 DISTRO= poky DISTRO_VERSION= 1.3+snapshot-20130316 TUNE_FEATURES = m32 i586 TARGET_FPU= meta meta-yocto= master:1ceb13dda11645229053fc4840954333f8910ba4 meta-realtime = schedtool:a766d16a1cf4da3c2dd13b8c7e53f89775733187 meta-yocto-bsp= master:1ceb13dda11645229053fc4840954333f8910ba4 NOTE: Resolving any missing task queue dependencies NOTE: Preparing runqueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks ERROR: Function failed: BUILDSPEC (see /home/insop/mybuilds/meta-realtime/tmp/work/i586-poky-linux/neard/0.9-gitAUTOINC+1e20e396cb837017b7e5ef822bfdab6ce060d2cf-r1/temp/log.do_package_write_rpm.31563 for further information) ERROR: Logfile of failure stored in: /home/insop/mybuilds/meta-realtime/tmp/work/i586-poky-linux/neard/0.9-gitAUTOINC+1e20e396cb837017b7e5ef822bfdab6ce060d2cf-r1/temp/log.do_package_write_rpm.31563 Log data follows: | DEBUG: Executing python function sstate_task_prefunc | DEBUG: Python function sstate_task_prefunc finished | DEBUG: Executing python function do_package_write_rpm | DEBUG: Executing python function read_subpackage_metadata | DEBUG: Python function read_subpackage_metadata finished | DEBUG: Executing python function do_package_rpm | DEBUG: Executing python function write_specfile | NOTE: Not creating empty RPM package for neard-tests | NOTE: Creating RPM package for neard-dbg | NOTE: Not creating empty RPM package for neard-staticdev | NOTE: Creating RPM package for neard-dev | NOTE: Not creating empty RPM package for neard-doc | NOTE: Not creating empty RPM package for neard-locale | NOTE: Creating RPM package for neard | NOTE: Creating RPM package for neard | DEBUG: Python function write_specfile finished | DEBUG: SITE files ['endian-little', 'bit-32', 'ix86-common', 'common-linux', 'common-glibc', 'i586-linux', 'common'] | DEBUG: Executing shell function BUILDSPEC | error: line 152: Illegal char '-' in EVR: Suggests: neard = 0.9-git0+1e20e396cb837017b7e5ef822bfdab6ce060d2cf-r1 | error: Package has no %description: neard-dbg.i586 | Building target platforms: i586-poky-linux | DEBUG: Python function do_package_rpm finished | DEBUG: Python function do_package_write_rpm finished | ERROR: Function failed: BUILDSPEC (see /home/insop/mybuilds/meta-realtime/tmp/work/i586-poky-linux/neard/0.9-gitAUTOINC+1e20e396cb837017b7e5ef822bfdab6ce060d2cf-r1/temp/log.do_package_write_rpm.31563 for further information) ERROR: Task 1370 (/home/insop/poky/meta/recipes-connectivity/neard/neard_0.9.bb, do_package_write_rpm) failed with exit code '1' NOTE: Tasks Summary: Attempted 3322 tasks of which 3281 didn't need to be rerun and 1 failed. Waiting for 0 running tasks to finish: Summary: 1 task failed:
Re: [yocto] [question] icecc: improve interaction with sstate
On Sun, Mar 17, 2013 at 4:17 PM, Martin Jansa martin.ja...@gmail.com wrote: On Fri, Mar 15, 2013 at 10:37:56PM -0700, Insop Song wrote: Hi, I am using HEAD of master, and I have this error after I use commit Please use better Subject next time, I was wondering what could be broken by my patch to icecc and your question is quite unrelated to that commit. Something like neard failing to build with latest poky would be better. Yes, agree and will do better next time. Thank you. Insop ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Agenda: Yocto Project Technical Team Meeting - Tuesday, March 19, 2013 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US Canada).
Agenda * Opens collection - 5 min (Song) * Yocto Project 1.3.1 release readiness - 10 min (CCB/all) * Yocto 1.4 status - 10 min (Song/team) https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.4_Status * SWAT team rotation: Andrei Dinu -Cristiana Voicu * Opens - 10 min * Team Sharing - 20 min -Original Appointment- We encourage people attending the meeting to logon the Yocto IRC chancel during the meeting (optional): Yocto IRC: http://webchat.freenode.net/?channels=#yocto IRC Tutorial: http://www.irchelp.org/irchelp/irctutorial.html 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. US Toll Free number: 1.877.561.6828 BlackBerry users, click this link to join your conference as a participant: 1.972.995.x76994298# 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-995 or 8784277 Beijing Out of Office dial 5878 4277 China (Shanghai): From office dial 8-995 or 3073322 Shanghai Out of Office dial 2307 3322 China (Shenzen): From office dial 8-995 or 6007877 Shenzen Out of Office dial 2600 7877 China (Other Cities): From IP phone dial 8-995 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 8995 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 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 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 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] SDK creation
Hi, Thanks for your reply.. But including this option didn't helped me.. On Mar 15, 2013 12:17 PM, Prana pra...@gmail.com wrote: Try adding this to your machine.conf PREFERRED_VERSION_qt4-embedded http://qt4-embedded_4.8.1.bb = 4.8.1 Thx, Prana Sent from my iPhone On Mar 15, 2013, at 12:06 AM, Navani Srivastava navani.srivast...@gmail.com wrote: Hi, I wish to create SDK with meta-toolchain-qte recipe. As two versions are provided by Poky-8.0. How can I direct compilation of SDK for qt4-embedded_4.8.1.bb ? Right now I am getting following error- ERROR: Multiple .bb files are due to be built which each provide qt4-embedded (/home/user/danny/meta/recipes-qt/qt4/qt4-embedded_4.8.1.bb/home/user/danny/meta/recipes-qt/qt4/ qt4-embedded_4.8.3.bb). Thanks and Regards Navani Kamal Srivastava ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] SDK creation
Hi all, Adding below lines helped.. PREFERRED_VERSION_qt4-embedded = 4.8.1 I was changing qt configuration options so was getting that error even after adding mentioned lines.. Thanks for the help Thanks and Regards Navani On Mar 15, 2013 12:17 PM, Prana pra...@gmail.com wrote: Try adding this to your machine.conf PREFERRED_VERSION_qt4-embedded http://qt4-embedded_4.8.1.bb = 4.8.1 Thx, Prana Sent from my iPhone On Mar 15, 2013, at 12:06 AM, Navani Srivastava navani.srivast...@gmail.com wrote: Hi, I wish to create SDK with meta-toolchain-qte recipe. As two versions are provided by Poky-8.0. How can I direct compilation of SDK for qt4-embedded_4.8.1.bb ? Right now I am getting following error- ERROR: Multiple .bb files are due to be built which each provide qt4-embedded (/home/user/danny/meta/recipes-qt/qt4/qt4-embedded_4.8.1.bb/home/user/danny/meta/recipes-qt/qt4/ qt4-embedded_4.8.3.bb). Thanks and Regards Navani Kamal Srivastava ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] New autobuilder.yoctoproject.org up and running
All, I'm pleased to announce that the migration to the new yocto-autobuilder code base is almost complete. A few minor issues have been identified and are either fixed and waiting for the current build to complete (nightly-intel-gpl) or about to be fixed (nightly-x32). The new autobuilder is located at: http://autobuilder.yoctoproject.org:8011 A few things. The old autobuilder still exists. If for some reason we need it, we do have a rollback plan in place. I am leaving up the master page in order to support any bugzilla entries that have links to the autobuilder. This will not stay up forever. I'm currently thinking of a longer term solution where the autobuilder can provide something like a pastebin of the errors, in order provide long term link management. Testing autobuilder runs is extraordinarily time consuming. Considering the support matrix (danny, denzil and current), time it takes to build each, plus the new support for mix and match layering, testing everything is impossible. If you see any issue, please, let me know immediately. This migration is occurring fairly late in the release cycle and I want to identify any issues within the next week or so, especially any missing/misplaced artifacts. I have been noticing some failed sanity issues in my test runs. I do not believe that this is caused by the new autobuilder code. In fact, I spent some time looking at it and discussing it with RP and we both feel that it is not caused by the new code. I've reduced the number of concurrent builds on the slaves to two for the time being to verify that the ab wasn't causing sanity failures. I'll try later in the week to bump those back up to 3 builds per slave. Things should run faster on the new autobuilder, especially once I bump things back up to 3 builds per slave. I won't be sure how fast for about a week or so, in order to get a good sample of data. If I had to guess, I know of one change on nightly that should save close to an hour. Also, you'll notice that meta-intel is no longer on the main autobuilder. We are moving it to its own master. Its outage will extend until Monday evening Pacific time. We did this for a few reasons, mainly to reduce load on the autobuilder master. I will announce the finalized url tomorrow. The code base for the new autobuilder currently lives in: http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder/log/?h=eflanagan/yocto-autobuilder-refactor Once this migration is complete and had some shake out time, we'll be moving it into master. Thanks, -b -- Elizabeth Flanagan Yocto Project Build and Release ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
