Re: [yocto] [yocto and jenkins]
On Tue, Jun 3, 2014 at 2:26 AM, Insop Song insop.s...@gmail.com wrote:
Setting export BB_ENV_EXTRAWHITE=${BUILD_NUMBER} fixed the issue.
and just for the record, the Linaro jenkins script set IMAGE_NAME in
the generated site.conf file, see [1]. this file is generated by the
Jenkins build scripts, prior to the build.
[1]
https://git.linaro.org/openembedded/jenkins-setup.git/blob/HEAD:/functions.sh#l304
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH V2] opkg-build: add detection if using GNU tar.
From: Thomas Ingleby thomas.c.ingl...@intel.com * Some options of GNU tar do not exist on other implementations Signed-off-by: Thomas Ingleby thomas.c.ingl...@intel.com --- opkg-build | 13 ++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/opkg-build b/opkg-build index e314712..ed1c93b 100755 --- a/opkg-build +++ b/opkg-build @@ -159,6 +159,13 @@ ogargs= outer=ar noclean=0 opkext=0 + +tarformat= +if tar --help 21 | grep -- --format /dev/null; +then +tarformat=--format=gnu +fi + usage=Usage: $0 [-c] [-C] [-O] [-o owner] [-g group] pkg_directory [destination_directory] while getopts cCg:ho:vO opt; do case $opt in @@ -233,8 +240,8 @@ tmp_dir=$dest_dir/IPKG_BUILD.$$ mkdir $tmp_dir echo $CONTROL $tmp_dir/tarX -( cd $pkg_dir tar $ogargs -X $tmp_dir/tarX -cz --format=gnu -f $tmp_dir/data.tar.gz . ) -( cd $pkg_dir/$CONTROL tar $ogargs -cz --format=gnu -f $tmp_dir/control.tar.gz . ) +( cd $pkg_dir tar $ogargs -X $tmp_dir/tarX -cz $tarformat -f $tmp_dir/data.tar.gz . ) +( cd $pkg_dir/$CONTROL tar $ogargs -cz $tarformat -f $tmp_dir/control.tar.gz . ) rm $tmp_dir/tarX echo 2.0 $tmp_dir/debian-binary @@ -249,7 +256,7 @@ rm -f $pkg_file if [ $outer = ar ] ; then ( cd $tmp_dir ar -crf $pkg_file ./debian-binary ./control.tar.gz ./data.tar.gz ) else - ( cd $tmp_dir tar -cz --format=gnu -f $pkg_file ./debian-binary ./control.tar.gz ./data.tar.gz ) + ( cd $tmp_dir tar -cz $tarformat -f $pkg_file ./debian-binary ./control.tar.gz ./data.tar.gz ) fi rm $tmp_dir/debian-binary $tmp_dir/data.tar.gz $tmp_dir/control.tar.gz -- 1.9.2 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Detailed steps involved in populate_sdk
Hello Raj, Thank you for your reply. May be I because I don't know about it but I am still not convinced about the on thing. When we say 'for normal build these consideration is not needed', this means the tools used in 'build host' and 'sdk hosts' are different (may be similar versions but different binary builds) right? (Even in the case when both 'build host' and 'sdk host' are exactly same for eg. basic Ubuntu 14.04 x86_64 with basic additional tools installed as suggested in yocto user manual). Would there be any option for me to tell yocto to generate all the tools and use exactly the same for 'build host' as well as 'sdk host'? Best Regards, Anooj From: Khem Raj raj.k...@gmail.com To: Anooj Gopi anooj.g...@alpine.de, Cc: yocto@yoctoproject.org Date: 01.06.2014 04:49 Subject:Re: [yocto] Detailed steps involved in populate_sdk On May 30, 2014 7:15 AM, Anooj Gopi anooj.g...@alpine.de wrote: Hello, I am new to yocto project and learning about the project step by step for one of our project. For study purpose, I'm currently using the latest yocto git clone and built bitbake core-image-minimal successfully for beaglebone. I have got all the target images to boot. At this point I assume that all the native tool chain binaries required to build the target image is already generated by yocto. Now when I try to create the SDK with the command bitbake core-image-minimal -c populate_sdk, I can see there is again native packages being configured and compiled. As per my understanding about yocto I was expecting this would have already done during bitbake core-image-minimal because all these tools are required to build the images. In my understanding populate_sdk would just install the native package deb files already created during bitbake core-image-minimal. I know there is something wrong in my understanding. Could you please explain bit in detail. sdks are supposed to run on different hosts too which we call sdkhost there fore it has to build native sdk packages to insulate itself from build host. for normal build these consideration is not needed Best Regards, Anooj Gopi Alpine Electronics RD Europe GmbH, Vor dem Lauch 14, 70567 Stuttgart, Registergericht Stuttgart, HRB 25265 Geschaeftsfuehrer: Satoshi Soma, Shuji Taguchi Working office: Vor dem Lauch 14, 70567 Stuttgart -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto Alpine Electronics RD Europe GmbH, Vor dem Lauch 14, 70567 Stuttgart, Registergericht Stuttgart, HRB 25265 Geschaeftsfuehrer: Satoshi Soma, Shuji Taguchi Working office: Vor dem Lauch 14, 70567 Stuttgart-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] bitbake virtual/kernel -c devshell doesn't build the sdk
hi, On mån, 2014-06-02 at 12:50 -0700, Alexandru Vaduva wrote: Adrian did you run a -c compile before -c devshell? No I have not. And it was intentional. I know that if I compile anything I will get the crossdk. I do not believe you should have a crosssdk with only calling -c devshell on a pachage/recipe. My understanding was the opposite. But if this is normal behaviour than I am ok with it. Alex --Adrian On Monday, June 2, 2014 8:21 PM, Adrian Dudau adrian.du...@enea.com wrote: Hi, Starting from a fresh build folder, I run bitbake -c devshell virtual/kernel and expect to have the cross SDK sourced and be able to build the kernel in the devshell. The issue is that even though PATH is preppended correctly with the expected location of the SDK (in my case tmp/sysroots/x86_64-linux/usr/bin/ppce500v2-enea-linux-gnuspe), the cross SDK is not built. Am I wrong assuming that -c devshell virtual/kernel should depend on the crosssdk? best regards, --Adrian -- ___ 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] [meta-raspberrypi] Purpose of vc-graphics-hardfp.bb vc-graphics.bb unclear
Hello all, my ongoing struggle to get qt5 working on the raspberrypi led me to a question unrelated to qt5. why do vc-graphics-hardfp.bb vc-graphics.bb exist? [1] There is no recipe which uses on of this files. If I add one of them to my image via IMAGE_INSTALL_append I get errors that userland.git and vc-grapics-hardfp both provide virtual/egl and virtual/libgles2. (Which they obviously do.) [2] My question is: What is the reason for having userland_git.bb vc-graphics.bb/vc-graphics-hardfp ? Two things are notable, IMHO: vc-graphics.inc has two files specified. One packageconfig (.pc) file with the right includes. I had to add one library manually in order to get qt5 compiling and the other one is a startup script for initalising the videocore. Are these two files deprecated by now? The last change to a file in the vc-graphics folder has been made 2013-08-21 Or do I need at least the initscript to get the videocore working? Regards, Felix Fischer [1] http://git.yoctoproject.org/cgit/cgit.cgi/meta-raspberrypi/tree/recipes-bcm/vc-graphics/ [2] http://git.yoctoproject.org/cgit/cgit.cgi/meta-raspberrypi/tree/recipes-graphics/userland/userland_git.bb Student Employee (VC-I42) Vehicle Cockpit - HMI Software and Code generation IAV GmbH Carnotstr. 1 10587 BERLIN GERMANY Phone: +49 30 3997-89540 Fax: +49 30 3997-89411 E-Mail: mailto:felix01.fisc...@iav.de Internet: http://www.iav.com Sitz/Registered Office: Berlin, Registergericht/Registration Court: Amtsgericht Charlottenburg, Registernummer/Company Registration Number: HRB 21 280, Geschäftsführer/Managing Directors: Kurt Blumenröder, Michael Schubert, Dr. Rüdiger Goyk Vorsitzender des Aufsichtsrates/Chairman of the Supervisory Board: Dr. Harald Ludanek-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi] Purpose of vc-graphics-hardfp.bb vc-graphics.bb unclear
On 03/06/2014 15:31, Felix01 Fischer wrote: Hello all, my ongoing struggle to get qt5 working on the raspberrypi led me to a question unrelated to qt5. why do vc-graphics-hardfp.bb vc-graphics.bb exist? [1] There is no recipe which uses on of this files. If I add one of them to my image via IMAGE_INSTALL_append I get errors that userland.git and vc-grapics-hardfp both provide virtual/egl and virtual/libgles2. (Which they obviously do.) [2] My question is: What is the reason for having userland_git.bb vc-graphics.bb/vc-graphics-hardfp ? Hi Felix, I'm not sure, but I've been looking at userland vs vc-graphics recently and I believe it is historical. Originally the intermediate layer between userspace and the videocore was distributed as binaries which is what vc-graphics pulls down ref: https://github.com/raspberrypi/firmware/tree/master/opt/vc More recently Broadcom opened up the source and provided it under a more relaxed license, and this is what userland provides: ref: http://www.raspberrypi.org/open-source-arm-userspace/ ref: https://github.com/raspberrypi/userland Somebody will no doubt correct me if my guess is wrong :) I have been using userland + gstreamer reasonably sucessfully here although my patch is needed for some of the userspace apps (e.g. raspivid), and there are some configuration issues that need patching still relating to gstreamer1.0-omx ref: https://github.com/raspberrypi/userland/pull/179 Cheers, Alex Two things are notable, IMHO: vc-graphics.inc has two files specified. One packageconfig (.pc) file with the right includes. I had to add one library manually in order to get qt5 compiling and the other one is a startup script for initalising the videocore. Are these two files deprecated by now? The last change to a file in the vc-graphics folder has been made 2013-08-21 Or do I need at least the initscript to get the videocore working? Regards, Felix Fischer [1] http://git.yoctoproject.org/cgit/cgit.cgi/meta-raspberrypi/tree/recipes-bcm/vc-graphics/ [2] http://git.yoctoproject.org/cgit/cgit.cgi/meta-raspberrypi/tree/recipes-graphics/userland/userland_git.bb Student Employee (VC-I42) Vehicle Cockpit - HMI Software and Code generation IAV GmbH Carnotstr. 1 10587 BERLIN GERMANY Phone: +49 30 3997-89540 Fax: +49 30 3997-89411 E-Mail: mailto:felix01.fisc...@iav.de Internet: http://www.iav.com http://www.iav.com/ Sitz/Registered Office: Berlin, Registergericht/Registration Court: Amtsgericht Charlottenburg, Registernummer/Company Registration Number: HRB 21 280, Geschäftsführer/Managing Directors: Kurt Blumenröder, Michael Schubert, Dr. Rüdiger Goyk Vorsitzender des Aufsichtsrates/Chairman of the Supervisory Board: Dr. Harald Ludanek -- Dynamic Devices Ltd http://www.dynamicdevices.co.uk/ Alex J Lennon / Director 1 Queensway, Liverpool L22 4RA mobile: +44 (0)7956 668178 Linkedin http://www.linkedin.com/in/alexjlennon Skype skype:alexjlennon?add This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. Company Name is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Fwd: [OE-core] TSC / OE Workgroup meeting today
-- Forwarded message -- From: Richard Purdie richard.pur...@linuxfoundation.org Date: Tue, Jun 3, 2014 at 2:51 AM Subject: [OE-core] TSC / OE Workgroup meeting today To: openembedded-c...@lists.openembedded.org, openembedded-de...@lists.openembedded.org Its the first week of the month so there should be a public OpenEmbedded TSC/workgroup IRC meeting today. If you're interested in discussing long-term technical efforts around the OpenEmbedded project please join us on irc.freenode.net in channel #oe. Timing is a little tricky as today, whilst I can make the old time of 17:00 GMT (9am PST, 11am CST, 12 EST, 18:00 CET) I can't make the later timeslot we moved to which was 2 hours later. I think Paul may not be around today. I therefore plan to be around at the 17:00 time slot and am happy to talk with anyone then, the other TSC members may be around then or at the later time slot. Cheers, Richard -- ___ Openembedded-core mailing list openembedded-c...@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core -- Jeff Osier-Mixon @Intel Yocto Project Community Manager http://yoctoproject.org -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Minutes: Yocto Project Technical Team Meeting - Tuesday, June 3, 2014 8:00 AM US Pacific Time
Attendees: Saul, Stephen, Armin, Ross, Alex D, Tom, Michael, Jefro, Alex G, Matthew, Cristian, Richard, Jessica, David, Bruce, LCyrin, Sean, * Opens collection - 5 min (Stephen) * Yocto 1.7 status - 5 min (Stephen/team) YP 1.7 Status - moved to new GCC 4.9. https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.7_Status https://wiki.yoctoproject.org/wiki/Yocto_1.7_Schedule https://wiki.yoctoproject.org/wiki/Yocto_1.7_Features * SWAT team rotation: Cristian - Nitin https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team * Opens - 10 min * Team Sharing - 10 min Richard - Sent an e-mail about Autobuilder change. If this change is made, a number of recipes may need updates. Need feedback on this change. Michael - Working on web hooks on yoctoproject.org. If your organization would like these hooks, please let Michael know. Thanks, Stephen K. Jolley Yocto Project Program Manager INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 * Work Telephone: (503) 712-0534 *Cell:(208) 244-4460 * Email: stephen.k.jol...@intel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Source Command Permission Denied
On 3 June 2014 16:39, Kashyap Gada gada.kash...@gmail.com wrote: bash: /home/kashyap/yocto/poky/scripts/oe-setup-builddir: Permission denied The permissions on that file don't involve +x. Is that a fresh checkout of poky or copied from the removable media? Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Source Command Permission Denied
its copied! On Tue, Jun 3, 2014 at 9:16 PM, Burton, Ross ross.bur...@intel.com wrote: On 3 June 2014 16:39, Kashyap Gada gada.kash...@gmail.com wrote: bash: /home/kashyap/yocto/poky/scripts/oe-setup-builddir: Permission denied The permissions on that file don't involve +x. Is that a fresh checkout of poky or copied from the removable media? Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Source Command Permission Denied
So you probably lost every executable mode when you did that. Make a fresh clone and reapply your changes, that will be easier than finding every file that isn't executable when it should be. Ross On 3 June 2014 16:49, Kashyap Gada gada.kash...@gmail.com wrote: its copied! On Tue, Jun 3, 2014 at 9:16 PM, Burton, Ross ross.bur...@intel.com wrote: On 3 June 2014 16:39, Kashyap Gada gada.kash...@gmail.com wrote: bash: /home/kashyap/yocto/poky/scripts/oe-setup-builddir: Permission denied The permissions on that file don't involve +x. Is that a fresh checkout of poky or copied from the removable media? Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] external-linaro-sdk-toolchain.bb, do_package_write_rpm) failed with exit code '1'
When try to build in Ubuntu 14.04 x86_64 machine following failure occurs.
| error: line 24: invalid tag value(^[A-Za-z0-9+._]+$) Version: Version:
'libpseudo.so'
| error: Package has no %description:
binutils-cross-canadian-arm.x86_64_nativesdk
I doubt following part of the bitbake fails due to some unknown issue
inherit cross-canadian
# ensure variable exists to avoid build error without external toolchain
TOOLCHAIN_PATH ?=
def elt_get_bfd_version(d):
import subprocess,os,bb
if os.path.exists(d.getVar('TOOLCHAIN_PATH', d,
1)+'/bin/'+d.getVar('TARGET_PREFIX', d, 1)+'as'):
return subprocess.Popen([d.getVar('TOOLCHAIN_PATH', d,
1)+'/bin/'+d.getVar('TARGET_PREFIX', d, 1)+'as', '-v', '--version'],
stderr=subprocess.STDOUT,stdout=subprocess.PIPE).communicate()[0].splitlines()[0].split()[3]
ELT_VER_BFD := ${@elt_get_bfd_version(d)}
Is any one face this issue in the past?
Alpine Electronics RD Europe GmbH, Vor dem Lauch 14, 70567 Stuttgart,
Registergericht Stuttgart, HRB 25265
Geschaeftsfuehrer: Satoshi Soma, Shuji Taguchi
Working office: Vor dem Lauch 14, 70567 Stuttgart--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] external-linaro-sdk-toolchain.bb, do_package_write_rpm) failed with exit code '1'
Please note that the same sources when built in Ubuntu 12.04 passes
without issue. Is this anything related to python version?
Note: The yocto project I am using is not the latest.
From: Anooj Gopi anooj.g...@alpine.de
To: yocto@yoctoproject.org,
Date: 03.06.2014 17:55
Subject:[yocto] external-linaro-sdk-toolchain.bb,
do_package_write_rpm) failed with exit code '1'
Sent by:yocto-boun...@yoctoproject.org
When try to build in Ubuntu 14.04 x86_64 machine following failure occurs.
| error: line 24: invalid tag value(^[A-Za-z0-9+._]+$) Version: Version:
'libpseudo.so'
| error: Package has no %description:
binutils-cross-canadian-arm.x86_64_nativesdk
I doubt following part of the bitbake fails due to some unknown issue
inherit cross-canadian
# ensure variable exists to avoid build error without external toolchain
TOOLCHAIN_PATH ?=
def elt_get_bfd_version(d):
import subprocess,os,bb
if os.path.exists(d.getVar('TOOLCHAIN_PATH', d,
1)+'/bin/'+d.getVar('TARGET_PREFIX', d, 1)+'as'):
return subprocess.Popen([d.getVar('TOOLCHAIN_PATH', d,
1)+'/bin/'+d.getVar('TARGET_PREFIX', d, 1)+'as', '-v', '--version'],
stderr=subprocess.STDOUT,stdout=subprocess.PIPE).communicate()[0].splitlines()[0].split()[3]
ELT_VER_BFD := ${@elt_get_bfd_version(d)}
Is any one face this issue in the past?
Alpine Electronics RD Europe GmbH, Vor dem Lauch 14, 70567 Stuttgart,
Registergericht Stuttgart, HRB 25265
Geschaeftsfuehrer: Satoshi Soma, Shuji Taguchi
Working office: Vor dem Lauch 14, 70567 Stuttgart--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Alpine Electronics RD Europe GmbH, Vor dem Lauch 14, 70567 Stuttgart,
Registergericht Stuttgart, HRB 25265
Geschaeftsfuehrer: Satoshi Soma, Shuji Taguchi
Working office: Vor dem Lauch 14, 70567 Stuttgart--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Source Command Permission Denied
On 06/03/2014 09:20 AM, Kashyap Gada wrote: Thank you Ross. I actually ran into another problem in bitbaking core-image-sato from the getting started guide at the yocto site which led me into changing to a setup which doesnot include mounting of any drive to my ubuntu distribution. the problem is as follows. While compiling of e2fsprogs-1.42.9-r0 do_compile (pid 5276) the details of the error log generated is as follows SNIP chmod: cannot operate on dangling symlink 'prof_err.h' chmod: prof_err.h: new permissions are r-xrwxrwx, not r-xr-xr-x chmod: prof_err.c: new permissions are r-xrwxrwx, not r-xr-xr-x Looks like your still having some sort of permissions issue. Where exactly are you doing your build? What type of filesystem? Sau! make[2]: *** [prof_err.h] Error 1 make[2]: *** Waiting for unfinished jobs make[2]: Leaving directory `/mnt/kashyap/hda/yocto/poky/build/tmp/work/i586-poky-linux/e2fsprogs/1.42.9-r0/build/misc' make[1]: *** [all-progs-recursive] Error 1 make[1]: Leaving directory `/mnt/kashyap/hda/yocto/poky/build/tmp/work/i586-poky-linux/e2fsprogs/1.42.9-r0/build' make: *** [all] Error 2 ERROR: oe_runmake failed WARNING: exit code 1 from a shell command. ERROR: Function failed: do_compile (log file is located at /mnt/kashyap/hda/yocto/poky/build/tmp/work/i586-poky-linux/e2fsprogs/1.42.9-r0/temp/log.do_compile.5276) Sorry for attaching this to this list. On Tue, Jun 3, 2014 at 9:20 PM, Burton, Ross ross.bur...@intel.com wrote: So you probably lost every executable mode when you did that. Make a fresh clone and reapply your changes, that will be easier than finding every file that isn't executable when it should be. Ross On 3 June 2014 16:49, Kashyap Gada gada.kash...@gmail.com wrote: its copied! On Tue, Jun 3, 2014 at 9:16 PM, Burton, Ross ross.bur...@intel.com wrote: On 3 June 2014 16:39, Kashyap Gada gada.kash...@gmail.com wrote: bash: /home/kashyap/yocto/poky/scripts/oe-setup-builddir: Permission denied The permissions on that file don't involve +x. Is that a fresh checkout of poky or copied from the removable media? Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Syntax error
Hi everybody! Dears, my name is Dario D'Abronzo and I'm working with an nvidia tegra 3 SOM. I've already built the image with the instructions of the developer and I succeded with oe-core. Now I'm trying to build an image importing the BSP in Yocto and compiling trough poky and HOB. When I add the layer from the manufacturer in HOB (meta toradex) I get a general error with no explaination, and when I try to bitbake I get: NOTE: Error during finalise of /home/ddalnx/poky/meta-toradex/recipes/images/console-trdx-image.bb NOTE: Error during finalise of /home/ddalnx/poky/meta-toradex/recipes/images/qt4e-demo-image.bb NOTE: Error during finalise of /home/ddalnx/poky/meta-toradex/recipes/images/angstrom-qt-x11-image.bb NOTE: Error during finalise of /home/ddalnx/poky/meta-toradex/recipes/images/angstrom-lxde-image.bb ERROR: ExpansionError during parsing /home/ddalnx/poky/meta-toradex/recipes/images/console-trdx-image.bb: Failure expanding variable do_rootfs: SyntaxError: invalid syntax (string, line 2) the BB file begin with: #Angstrom image DESCRIPTION = Image booting to a console So the line 2 is just the description code. Why am I failing bitbaking from ~/poky/build/ ?? I'm giving exactly the same code as oe-core: ddalnx@ddassgdeb:~$ cd poky/ ddalnx@ddassgdeb:~/poky$ source oe-init-build-env . . etc ... . ddalnx@ddassgdeb:~/poky/build$ bitbake angstrom-qt-x11-image if you're interested on analyzing the source I gitted from http://git.toradex.com/gitweb specifically from gt:// git.toradex.com/gitweb/meta-toradex.git PS. I verified that I'm using the correct python version and I do, it's the v. 2.7.3 and the bitbake folder is unaltered in both oe-core and in poky folder. Many thanks for your precious help, Kind Regards, Dario. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Installer Ext Image for USB Device
Hi, The yocto build has facilities to generate an ext2 filesystem for the rootfs without the need to have root privilege while running the build. I need to be able to generate an alternate ext2 filesystem with various files in it as another byproduct of the same build. What facility in the build system would be suitable to build on for this and would run without requiring root privilege? I am OK with a manual 'dd' step at the end using 'sudo' to write to physical HW (just like I have to do for SD cards at present). Thanks in advance. -- Regards, Darcy --- Darcy Watkins Staff Engineer, Firmware In Motion Technology, a Sierra Wireless company 350-625 Agnes St. New Westminster, BC Canada, V3M 5Y4 [P1] -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 3/3] PublishArtifacts: add md5sums artifact
REF: Bug ID 6354 Added a md5sums artifact into PublishArtifacts Signed-off-by: Lynn 'Cyrin' Conway lynncy...@gmail.com --- .../autobuilder/buildsteps/PublishArtifacts.py |6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/lib/python2.7/site-packages/autobuilder/buildsteps/PublishArtifacts.py b/lib/python2.7/site-packages/autobuilder/buildsteps/PublishArtifacts.py index db86ec2..bb69d18 100644 --- a/lib/python2.7/site-packages/autobuilder/buildsteps/PublishArtifacts.py +++ b/lib/python2.7/site-packages/autobuilder/buildsteps/PublishArtifacts.py @@ -180,6 +180,10 @@ class PublishArtifacts(ShellCommand): command=command+cp -R --no-dereference + \ os.path.join(self.basedir, conf/) + \ /* + DEST + / + MACHINE_PUBLISH_DIR + / + artifact_name + /conf; +elif artifact == md5sums: +artifact_name, deploy_image_dir = self.getDeployNames(artifact, buildername) +command = command + for x in `find + deploy_image_dir + -type f`; do +command = command + filenm=`basename $x`; md5sum $x $filenm.md5sum; done elif artifact == None: command=command+echo 'Skipping copy of + artifact + .' else: @@ -216,7 +220,7 @@ class PublishArtifacts(ShellCommand): artifact_name = artifact_name + -lsb if self.layerversion_core is not None and int(self.layerversion_core) 2: deploy_dir_image = os.path.join(os.path.join(self.basedir, tmp/deploy/images/), artifact) -else: +else:1 deploy_dir_image = os.path.join(self.basedir, tmp/deploy/images/) return artifact_name, deploy_dir_image -- 1.7.9.5 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 1/3] buildset-config.master/*: change call to MD5 creation
REF: Bug ID 6354
The code for MD5 creation is being moved from MakeImageMD5s to
PublishArtifacts['md5sums']. This commit changes every file in
buildset-config.master that had a call to MakeImageMD5s.
Signed-off-by: Lynn 'Cyrin' Conway lynncy...@gmail.com
---
buildset-config.master/build-appliance.conf |4 ++--
buildset-config.master/buildtools.conf |4 ++--
buildset-config.master/minnow-lsb.conf |4 ++--
buildset-config.master/minnow.conf |4 ++--
buildset-config.master/nightly-arm-lsb.conf |4 ++--
buildset-config.master/nightly-arm.conf |4 ++--
buildset-config.master/nightly-fsl-arm-lsb.conf |4 ++--
buildset-config.master/nightly-fsl-arm.conf |4 ++--
buildset-config.master/nightly-fsl-ppc-lsb.conf |4 ++--
buildset-config.master/nightly-fsl-ppc.conf |4 ++--
buildset-config.master/nightly-mips-lsb.conf|4 ++--
buildset-config.master/nightly-mips.conf|4 ++--
buildset-config.master/nightly-ppc-lsb.conf |4 ++--
buildset-config.master/nightly-ppc.conf |4 ++--
buildset-config.master/nightly-x32.conf |5 +++--
buildset-config.master/nightly-x86-64-lsb.conf |4 ++--
buildset-config.master/nightly-x86-64.conf |4 ++--
buildset-config.master/nightly-x86-lsb.conf |4 ++--
buildset-config.master/nightly-x86.conf |4 ++--
buildset-config.master/poky-tiny.conf |4 ++--
20 files changed, 41 insertions(+), 40 deletions(-)
diff --git a/buildset-config.master/build-appliance.conf
b/buildset-config.master/build-appliance.conf
index d681b87..f63be2c 100644
--- a/buildset-config.master/build-appliance.conf
+++ b/buildset-config.master/build-appliance.conf
@@ -17,6 +17,6 @@ steps: [{'SetDest':{}},
{'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
{'BuildImages': {'images': 'universe -c fetch'}},
{'BuildImages': {'images': 'build-appliance-image'}},
-{'PublishLayerTarballs':{}}, {'MakeImageMD5s':{}},
-{'PublishArtifacts': {'artifacts': ['build-appliance']}}]
+{'PublishLayerTarballs':{}},
+{'PublishArtifacts': {'artifacts': ['build-appliance', 'md5sums']}}]
diff --git a/buildset-config.master/buildtools.conf
b/buildset-config.master/buildtools.conf
index f71e535..673b6bc 100644
--- a/buildset-config.master/buildtools.conf
+++ b/buildset-config.master/buildtools.conf
@@ -11,5 +11,5 @@ steps: [{'SetDest':{}},
{'CreateAutoConf': {'machine': 'qemux86-64', 'SDKMACHINE' : 'x86_64',
'distro': 'poky', 'buildapp': True}},
{'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
{'BuildImages': {'images': 'buildtools-tarball'}},
-{'PublishLayerTarballs':{}}, {'MakeImageMD5s':{}},
-{'PublishArtifacts': {'artifacts': ['buildtools-tarball']}}]
+{'PublishLayerTarballs':{}},
+{'PublishArtifacts': {'artifacts': ['buildtools-tarball', 'md5sums']}}]
diff --git a/buildset-config.master/minnow-lsb.conf
b/buildset-config.master/minnow-lsb.conf
index d1f12aa..0293f38 100644
--- a/buildset-config.master/minnow-lsb.conf
+++ b/buildset-config.master/minnow-lsb.conf
@@ -20,6 +20,6 @@ steps: [{'SetDest':{}},
{'CreateAutoConf': {'machine': 'minnow', 'SDKMACHINE' : 'x86_64',
'distro': 'poky-lsb', 'emgd': 'True', 'pvr': 'False', 'atextappend':
'\nNOISO=1\nCORE_IMAGE_EXTRA_INSTALL += dmidecode pciutils ethtool
alsa-utils\n'}},
{'CreateBBLayersConf': {'buildprovider' : 'yocto', 'bsplayer': True,
'bspprovider': 'intel','layerdirs': ['meta-minnow', 'meta-intel',
'meta-intel/meta-tlk']}},
{'BuildImages': {'images': 'core-image-lsb core-image-lsb-dev
core-image-lsb-sdk core-image-lsb-qt3'}},
-{'PublishLayerTarballs':{}}, {'MakeImageMD5s':{}},
-{'PublishArtifacts': {'artifacts': ['conf', 'minnow']}}]
+{'PublishLayerTarballs':{}},
+{'PublishArtifacts': {'artifacts': ['conf', 'minnow', 'md5sums']}}]
diff --git a/buildset-config.master/minnow.conf
b/buildset-config.master/minnow.conf
index fcb83bd..c09a338 100644
--- a/buildset-config.master/minnow.conf
+++ b/buildset-config.master/minnow.conf
@@ -20,6 +20,6 @@ steps: [{'SetDest':{}},
{'CreateAutoConf': {'machine': 'minnow', 'SDKMACHINE' : 'x86_64',
'distro': 'poky', 'emgd': 'True', 'pvr': 'False', 'atextappend':
'\nNOISO=1\nCORE_IMAGE_EXTRA_INSTALL += dmidecode pciutils ethtool
alsa-utils\n'}},
{'CreateBBLayersConf': {'buildprovider' : 'yocto', 'bsplayer': True,
'bspprovider': 'intel','layerdirs': ['meta-minnow', 'meta-intel',
'meta-intel/meta-tlk']}},
{'BuildImages': {'images': 'core-image-sato core-image-sato-dev
core-image-sato-sdk core-image-minimal core-image-minimal-dev'}},
-{'PublishLayerTarballs':{}}, {'MakeImageMD5s':{}},
-{'PublishArtifacts': {'artifacts': ['minnow', 'ipk', 'rpm', 'deb']}}]
+{'PublishLayerTarballs':{}},
+{'PublishArtifacts':
[yocto] [PATCH 2/3] MakeImageMD5s: delete file
REF: Bug ID 6354
The functionality of MakeImageMDs is being moved into PublishArtifacts.
Since MakeImageMD5s is no longer needed, this commit deletes it.
Signed-off-by: Lynn 'Cyrin' Conway lynncy...@gmail.com
---
.../autobuilder/buildsteps/MakeImageMD5s.py| 42
1 file changed, 42 deletions(-)
delete mode 100644
lib/python2.7/site-packages/autobuilder/buildsteps/MakeImageMD5s.py
diff --git
a/lib/python2.7/site-packages/autobuilder/buildsteps/MakeImageMD5s.py
b/lib/python2.7/site-packages/autobuilder/buildsteps/MakeImageMD5s.py
deleted file mode 100644
index 84839fb..000
--- a/lib/python2.7/site-packages/autobuilder/buildsteps/MakeImageMD5s.py
+++ /dev/null
@@ -1,42 +0,0 @@
-'''
-Created on May 5, 2014
-
-__author__ = Elizabeth 'pidge' Flanagan
-__copyright__ = Copyright 2012-2014, Intel Corp.
-__credits__ = [Elizabeth Flanagan]
-__license__ = GPL
-__version__ = 2.0
-__maintainer__ = Elizabeth Flanagan
-__email__ = elizabeth.flana...@intel.com
-'''
-
-from buildbot.steps.shell import ShellCommand
-from twisted.python import log
-import os, datetime
-from autobuilder.config import *
-
-class MakeImageMD5s(ShellCommand):
-haltOnFailure = False
-flunkOnFailure = True
-name = Make Image MD5s
-def __init__(self, factory, argdict=None, **kwargs):
-self.factory = factory
-self.description = Making image md5sum file
-self.slavedir=os.path.join(os.path.join(YOCTO_ABBASE, yocto-slave))
-for k, v in argdict.iteritems():
-setattr(self, k, v)
-self.timeout = 10
-kwargs['timeout']=self.timeout
-ShellCommand.__init__(self, **kwargs)
-
-def start(self):
-DEST=self.getProperty(DEST)
-buildername=self.getProperty(buildername)
-command=
-if str(os.environ.get('PUBLISH_BUILDS')) == True:
-command = command + for x in `find build/tmp/deploy/images -type
f`; do
-command = command + filenm=`basename $x`; md5sum $x
$filenm.md5sum; done
-else:
-command=echo 'Not publishing build, skipping step'
-self.command = command
-ShellCommand.start(self)
--
1.7.9.5
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
