[yocto] How can I change the default ext4 or etx3 of the rootfs to ext2 or jffs2 in yocto build?
I want to minimize the size of the image built in core-image-minimal. However, I have no idea how to change the local.conf file or recipe file. Can anyone help me? -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How can I change the default ext4 or etx3 of the rootfs to ext2 or jffs2 in yocto build?
Hi, An easy way will be to refer Yocto documentation: http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html and for required rootfs changes, use IMAGE_FSTYPES: http://www.yoctoproject.org/docs/2.4/mega-manual/mega-manual.html#var-IMAGE_FSTYPES >From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] >On Behalf Of Nguy?n Thanh Vu >Sent: Thursday, January 11, 2018 10:05 AM >To: yocto@yoctoproject.org >Subject: [yocto] How can I change the default ext4 or etx3 of the rootfs to >ext2 or jffs2 in yocto build? >I want to minimize the size of the image built in core-image-minimal. However, >I have no idea how to change the >local.conf file or recipe file. Can anyone >help me? Best Regards, Maxin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] libgcc.a size
Hello I just upgraded from krogoth to rocko, and noticed the resulting rootfs image increased significantly. What stands out is a big bump in size for /usr/lib/arm-poky-linux-gnueabi/7.2.0/libgcc.a from 5 MB in krogoth(gcc 5.3.0) to 25 MB in rocko. Can someone shed some light ? What can be done ? Thanks -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-oic] Question about Iotivity 1.3.0/1 and fixes status
On 11/01/18 02:30, Chanho Park wrote: > Hi Philippe, > Hi Chanho Park, HNY to you > I found you already prepared iotivity 1.3.0, 1.3.1 recipes and fixes > in your github tree[1]. Yes they are still under review, did you test them ? Maybe I should resend them, now. > I wonder why you don’t post them in the meta-oic. Well I shared patches to list couple of time: https://lists.yoctoproject.org/pipermail/yocto/2017-June/036896.html https://lists.yoctoproject.org/pipermail/yocto/2017-September/037829.html https://lists.yoctoproject.org/pipermail/yocto/2017-December/039355.html > Do you have a plan to upstream them? I need reviewer to approve and commit them (@Kishen ?) or may I do it by my own since nobody objected on previous changes ? Side note, I also simplified a recipe for iotivity master branch (it now relies on scons install like tizen, debian etc) so if it helps I will update devel branch and this page soon: https://wiki.iotivity.org/wiki/yocto > Best Regards, BR, Keep in touch your feedback is valuable. > Chanho Park > > [1]: > https://github.com/TizenTeam/meta-oic/tree/sandbox/pcoval/on/master/review -- mailto:philippe.co...@osg.samsung.com gpg:0x467094BC https://blogs.s-osg.org/author/pcoval/ -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] libgcc.a size
> What stands out is a big bump in size for > /usr/lib/arm-poky-linux-gnueabi/7.2.0/libgcc.a from 5 MB in krogoth(gcc > 5.3.0) to 25 MB in rocko. Static library, probably compiled with -g (debug info included). You need to recompile libgcc excluding -g option... My best guess. Zoran On Thu, Jan 11, 2018 at 10:04 AM, Mircea Gliga wrote: > Hello > > I just upgraded from krogoth to rocko, and noticed the resulting rootfs > image increased significantly. > What stands out is a big bump in size for > /usr/lib/arm-poky-linux-gnueabi/7.2.0/libgcc.a from 5 MB in krogoth(gcc > 5.3.0) to 25 MB in rocko. > Can someone shed some light ? What can be done ? > > Thanks > > -- > ___ > 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] libgcc.a size
Hi guys >libgcc.a is "out-f-the-box" in rocko 25MB, but why should it be integrated in rootfs ? I asked myself the same question. Not clear for me yet how and why it gets in the rootfs. Thanks and regards Mircea On 11/01/18 13:51, Stefano Babic wrote: Hi Zoran, Mircea, On 11/01/2018 11:16, Zoran Stojsavljevic wrote: What stands out is a big bump in size for /usr/lib/arm-poky-linux-gnueabi/7.2.0/libgcc.a from 5 MB in krogoth(gcc 5.3.0) to 25 MB in rocko. Static library, probably compiled with -g (debug info included). You need to recompile libgcc excluding -g option... My best guess. libgcc.a is "out-f-the-box" in rocko 25MB, but why should it be integrated in rootfs ? The libc-2.26.so is still 1.2MB (ARM) and footprint is comparable to the past. Stefano -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] libgcc.a size
Hi Zoran, Mircea, On 11/01/2018 11:16, Zoran Stojsavljevic wrote: >> What stands out is a big bump in size for >> /usr/lib/arm-poky-linux-gnueabi/7.2.0/libgcc.a from 5 MB in krogoth(gcc >> 5.3.0) to 25 MB in rocko. > > Static library, probably compiled with -g (debug info included). You > need to recompile libgcc excluding -g option... My best guess. > libgcc.a is "out-f-the-box" in rocko 25MB, but why should it be integrated in rootfs ? The libc-2.26.so is still 1.2MB (ARM) and footprint is comparable to the past. Stefano -- = DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sba...@denx.de = -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] libgcc.a size
Hi Mircea, On 11/01/2018 12:54, Mircea Gliga wrote: > Hi guys > >>libgcc.a is "out-f-the-box" in rocko 25MB, but why should it be > integrated in rootfs ? > > I asked myself the same question. Not clear for me yet how and why it > gets in the rootfs. It is not - I have not in my -rocko projects. I guess you have some setup in your local.conf, like you added "dev-pkgs" or "staticdev-pkgs" somewhere. Stefano -- = DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sba...@denx.de = -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] fstab entry not mounting at boot-up
On 05-01-18 20:43, Edward Wingate wrote: My system has a USB-SSD drive and I added this to my fstab: /dev/sda1 /mnt/driveauto defaults,nonempty 0 0 But it doesn't get mounted on start-up. I can use "mount -a" after start-up and it mounts successfully. Everything else in fstab gets mounted on boot. Does anyone know why my new entry doesn't? Wild guess: "/mnt/drive" does not exist yet when the fstab is processed during startup. That will cause mount to fail. Kind regards, Mike Looijmans System Expert TOPIC Products Materiaalweg 4, NL-5681 RJ Best Postbus 440, NL-5680 AK Best Telefoon: +31 (0) 499 33 69 79 E-mail: mike.looijm...@topicproducts.com Website: www.topicproducts.com Please consider the environment before printing this e-mail -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [layerindex-web] Updating layers?
Hello! Is the layerindex not running the update script? I see end of September as last updates, and a bunch of branches in our layer (meta-timesys) were never picked up. Or is there another way for maintainers to add branches / trigger an update? Thanks, -- Steve Bedford Timesys Corporation -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Issues building Extensible SDK
Hi Robert,
Thank you very much, adding the lines
require conf/distro/include/yocto-uninative.inc
INHERIT += "uninative"
to the distro configuration enables the build to succeed.
Br,
Martin
From: Robert Yang
Sent: Thursday, January 11, 2018 6:45:29 AM
To: Martin Siegumfeldt; yocto@yoctoproject.org
Subject: Re: [yocto] Issues building Extensible SDK
Hi Martin,
Try:
$ bitbake -e | grep '^INHERIT=.*uninative'
If there is nothing, then add the following line to conf/local.conf:
INHERIT += "uninative"
// Robert
On 01/10/2018 03:46 PM, Martin Siegumfeldt wrote:
> Hi,
>
> We have a custom piece of (Zynq based) HW that we render a custom distro
> using Yocto. I am trying to build the extensible SDK but run into the below
> error:
>
> pokyuser@03c19f8798ba:/workdir/krogoth/build$ bitbake core-image-minimal -c
> populate_sdk_ext
> Loading cache: 100%
> ||
> Time: 0:00:00
> Loaded 2675 entries from dependency cache.
> Parsing recipes: 100%
> |##|
> Time: 0:00:01
> Parsing of 1915 .bb files complete (1913 cached, 2 parsed). 2677 targets, 377
> skipped, 0 masked, 0 errors.
> NOTE: Resolving any missing task queue dependencies
>
> Build Configuration:
> BB_VERSION= "1.34.0"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING = "ubuntu-16.04"
> TARGET_SYS= "arm-oe-linux-gnueabi"
> MACHINE = "zynq-soft-z7000-mb-v2"
> DISTRO= "gomspace"
> DISTRO_VERSION= "2.0"
> TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard cortexa9"
> TARGET_FPU= "hard"
> meta = "pyro:9c75151116aa293dc8567c237d7e4da5bdec90e3"
> meta-xilinx = "pyro:18097af3120a394a8e6933b7abc85e73e508c7e3"
> meta-oe
> meta-filesystems
> meta-networking
> meta-python = "pyro:dfbdd28d206a74bf264c2f7ee0f7b3e5af587796"
> meta-z7000= "pyro:b255ea4575b40d77a2f5dc9200de0718f979f175"
>
> Initialising tasks: 100%
> |###|
> Time: 0:00:03
> NOTE: Executing SetScene Tasks
> NOTE: Executing RunQueue Tasks
> ERROR: core-image-minimal-1.0-r0 do_populate_sdk_ext: Error executing a
> python function in exec_python_func() autogenerated:
>
> The stack trace of python calls that resulted in this exception/failure was:
> File: 'exec_python_func() autogenerated', lineno: 2, function:
> 0001:
> *** 0002:copy_buildsystem(d)
> 0003:
> File:
> '/workdir/krogoth/openembedded-core/meta/classes/populate_sdk_ext.bbclass',
> lineno: 298, function: copy_buildsystem
> 0294:f.write('TCLIBCAPPEND = ""\n')
> 0295:f.write('DL_DIR = "${TOPDIR}/downloads"\n')
> 0296:
> 0297:f.write('INHERIT += "%s"\n' % 'uninative')
> *** 0298:f.write('UNINATIVE_CHECKSUM[%s] = "%s"\n\n' %
> (d.getVar('BUILD_ARCH'), uninative_checksum))
> 0299:f.write('CONF_VERSION = "%s"\n\n' %
> d.getVar('CONF_VERSION', False))
> 0300:
> 0301:# Some classes are not suitable for SDK, remove them
> from INHERIT
> 0302:f.write('INHERIT_remove = "%s"\n' %
> d.getVar('SDK_INHERIT_BLACKLIST', False))
> Exception: UnboundLocalError: local variable 'uninative_checksum' referenced
> before assignment
>
> ERROR: core-image-minimal-1.0-r0 do_populate_sdk_ext: Function failed:
> copy_buildsystem
> ERROR: Logfile of failure stored in:
> /workdir/krogoth/build/tmp-glibc/work/zynq_soft_z7000_mb_v2-oe-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_populate_sdk_ext.8408
> ERROR: Task
> (/workdir/krogoth/openembedded-core/meta/recipes-core/images/core-image-minimal.bb:do_populate_sdk_ext)
> failed with exit code '1'
> NOTE: Tasks Summary: Attempted 2214 tasks of which 2210 didn't need to be
> rerun and 1 failed.
>
> Summary: 1 task failed:
>
> /workdir/krogoth/openembedded-core/meta/recipes-core/images/core-image-minimal.bb:do_populate_sdk_ext
> Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
>
>
> The standard SDK builds successfully all the way back from Fido throughout
> Rocko, however we would now like to build the Extensible SDK. Krogoth version
> builds it successfully, but Pyro and Rocko throws the above error (haven't
> tested Morty).
>
> I am unable to reproduce using Poky and thus assume it to
[yocto] [PATCH V2] beaglebone: Fix serial console device node
The serial console on BBB is now on /dev/ttyS0 , not /dev/ttyO0, which comes from legacy omap-serial driver. Support both options using SERIAL_CONSOLES. For details of the change to /dev/ttyS0, see Linux kernel commit 61929cf0169d91366fd3f30d6ee60681b037bc19 Author: Sebastian Andrzej Siewior Date: Mon Sep 29 20:06:39 2014 +0200 tty: serial: Add 8250-core based omap driver ... The device name is ttyS based instead of ttyO. If a ttyO based node name is required please ask udev for it. If both driver are activated (this and omap-serial) then this serial driver will take control over the device due to the link order Signed-off-by: Marek Vasut Cc: Joshua Lock Cc: Richard Purdie --- V2: Use SERIAL_CONSOLES to handle both old and new variant of the serial console node used. --- meta-yocto-bsp/conf/machine/beaglebone-yocto.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf b/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf index 990c967416..31856cf94b 100644 --- a/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf +++ b/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf @@ -20,7 +20,7 @@ WKS_FILE ?= "beaglebone-yocto.wks" IMAGE_INSTALL_append = " kernel-devicetree kernel-image-zimage" do_image_wic[depends] += "mtools-native:do_populate_sysroot dosfstools-native:do_populate_sysroot" -SERIAL_CONSOLE = "115200 ttyO0" +SERIAL_CONSOLES = "115200;ttyS0 115200;ttyO0" PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto" PREFERRED_VERSION_linux-yocto ?= "4.12%" -- 2.11.0 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH] beaglebone: Fix serial console device node
On 01/08/2018 12:28 PM, Martin Hundebøll wrote: > Hi Marek, > > On 2018-01-07 17:16, Marek Vasut wrote: >> The serial console on BBB is on /dev/ttyS0 , not /dev/ttyO0 . >> This changed again, so fix this. >> >> Signed-off-by: Marek Vasut >> Cc: Joshua Lock >> Cc: Richard Purdie >> --- >> meta-yocto-bsp/conf/machine/beaglebone-yocto.conf | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf >> b/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf >> index 990c967416..4f6c05f3ea 100644 >> --- a/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf >> +++ b/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf >> @@ -20,7 +20,7 @@ WKS_FILE ?= "beaglebone-yocto.wks" >> IMAGE_INSTALL_append = " kernel-devicetree kernel-image-zimage" >> do_image_wic[depends] += "mtools-native:do_populate_sysroot >> dosfstools-native:do_populate_sysroot" >> -SERIAL_CONSOLE = "115200 ttyO0" >> +SERIAL_CONSOLE = "115200 ttyS0" > > You can add both to SERIAL_CONSOLES instead: > > SERIAL_CONSOLES = "115200;ttyS0 115200;ttyO0" > > Maybe add a comment with hints about which kernels versions that make > the change(s). > > OE-core wraps *getty with in script that checks for the existence of the > configured devices before starting *getty. > > This also makes the recipe work on kernel versions still using ttyO0. Done, V2 is out. -- Best regards, Marek Vasut -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] applying patches depending on the image's name
Hello, I have several images (image-a.bb and image-b.bb) in a yocto layer and want to apply different patches to the kernel depending on the current image name. How can that be done? Thank you in advance. -- Vadim signature.asc Description: PGP signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Recipe for JNI Wrapper (libusb4java)
I'm trying to create a recipe for libusb4Java (
https://github.com/usb4java/libusb4java/).
I have the following recipe
SUMMARY = "Native library support for usb4java"
HOMEPAGE = "http://usb4java.org";
BUGTRACKER = "https://github.com/usb4java/libusb4java/issues";
SECTION = "libs"
DEPENDS = "libusb"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://LICENSE.md;md5=4c49d7fe1fc7a6ebad3b4e6b849a0052"
BBCLASSEXTEND = "native nativesdk"
SRCREV = "396d642a57678a0d9663b062c980fe100cc0ea1e"
SRC_URI = "git://github.com/usb4java/libusb4java.git"
S = "${WORKDIR}/git"
#need to change following ref http://usb4java.org/nativelibs.html
D = "/tmp"
export JAVA_HOME="${STAGING_DIR_NATIVE}/usr/bin/java"
inherit cmake java-library
local.conf has the following added:
BB_ENV_EXTRAWHITE += "JAVA_HOME"
I get the following error:
checking if
/home/ubuntu/yocto/poky/build/tmp/work/x86_64-linux/classpath-native/0.99-r6.0/recipe-sysroot-native/usr/bin/ecj-initial
works... configure: error: The Java compiler
/home/ubuntu/yocto/poky/build/tmp/work/x86_64-linux/classpath-native/0.99-r6.0/recipe-sysroot-native/usr/bin/ecj-initial
failed (see config.log, check the CLASSPATH?)
So I appear to have a classpath problem, but I'm unsure how to resolve this?
Any advice appreciated.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] applying patches depending on the image's name
No, because images are built from packages, and the packages have already been built by the time the image is considered. Using master you can build two different kernels in the same build and have different kernels in different images. Ross On 9 January 2018 at 15:54, Vadim Intelegator < v.intelega...@sirinsoftware.com> wrote: > Hello, > > I have several images (image-a.bb and image-b.bb) in a yocto layer and > want to apply different patches to the kernel depending on the current > image name. > How can that be done? > > Thank you in advance. > > -- > Vadim > > -- > ___ > 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] Issues building Extensible SDK
On Thu, Jan 11, 2018 at 12:56 AM, Martin Siegumfeldt wrote:
> Hi Robert,
>
>
> Thank you very much, adding the lines
>
>
> require conf/distro/include/yocto-uninative.inc
> INHERIT += "uninative"
>
> to the distro configuration enables the build to succeed.
>
I thought uninative was optional. Is it mandatory for SDK now ?
>
> Br,
>
> Martin
>
>
> From: Robert Yang
> Sent: Thursday, January 11, 2018 6:45:29 AM
> To: Martin Siegumfeldt; yocto@yoctoproject.org
> Subject: Re: [yocto] Issues building Extensible SDK
>
> Hi Martin,
>
> Try:
>
> $ bitbake -e | grep '^INHERIT=.*uninative'
>
> If there is nothing, then add the following line to conf/local.conf:
>
> INHERIT += "uninative"
>
> // Robert
>
> On 01/10/2018 03:46 PM, Martin Siegumfeldt wrote:
>> Hi,
>>
>> We have a custom piece of (Zynq based) HW that we render a custom distro
>> using Yocto. I am trying to build the extensible SDK but run into the below
>> error:
>>
>> pokyuser@03c19f8798ba:/workdir/krogoth/build$ bitbake core-image-minimal
>> -c populate_sdk_ext
>> Loading cache: 100%
>> ||
>> Time: 0:00:00
>> Loaded 2675 entries from dependency cache.
>> Parsing recipes: 100%
>> |##|
>> Time: 0:00:01
>> Parsing of 1915 .bb files complete (1913 cached, 2 parsed). 2677 targets,
>> 377 skipped, 0 masked, 0 errors.
>> NOTE: Resolving any missing task queue dependencies
>>
>> Build Configuration:
>> BB_VERSION= "1.34.0"
>> BUILD_SYS = "x86_64-linux"
>> NATIVELSBSTRING = "ubuntu-16.04"
>> TARGET_SYS= "arm-oe-linux-gnueabi"
>> MACHINE = "zynq-soft-z7000-mb-v2"
>> DISTRO= "gomspace"
>> DISTRO_VERSION= "2.0"
>> TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard
>> cortexa9"
>> TARGET_FPU= "hard"
>> meta = "pyro:9c75151116aa293dc8567c237d7e4da5bdec90e3"
>> meta-xilinx = "pyro:18097af3120a394a8e6933b7abc85e73e508c7e3"
>> meta-oe
>> meta-filesystems
>> meta-networking
>> meta-python = "pyro:dfbdd28d206a74bf264c2f7ee0f7b3e5af587796"
>> meta-z7000= "pyro:b255ea4575b40d77a2f5dc9200de0718f979f175"
>>
>> Initialising tasks: 100%
>> |###|
>> Time: 0:00:03
>> NOTE: Executing SetScene Tasks
>> NOTE: Executing RunQueue Tasks
>> ERROR: core-image-minimal-1.0-r0 do_populate_sdk_ext: Error executing a
>> python function in exec_python_func() autogenerated:
>>
>> The stack trace of python calls that resulted in this exception/failure
>> was:
>> File: 'exec_python_func() autogenerated', lineno: 2, function:
>> 0001:
>> *** 0002:copy_buildsystem(d)
>> 0003:
>> File:
>> '/workdir/krogoth/openembedded-core/meta/classes/populate_sdk_ext.bbclass',
>> lineno: 298, function: copy_buildsystem
>> 0294:f.write('TCLIBCAPPEND = ""\n')
>> 0295:f.write('DL_DIR = "${TOPDIR}/downloads"\n')
>> 0296:
>> 0297:f.write('INHERIT += "%s"\n' % 'uninative')
>> *** 0298:f.write('UNINATIVE_CHECKSUM[%s] = "%s"\n\n' %
>> (d.getVar('BUILD_ARCH'), uninative_checksum))
>> 0299:f.write('CONF_VERSION = "%s"\n\n' %
>> d.getVar('CONF_VERSION', False))
>> 0300:
>> 0301:# Some classes are not suitable for SDK, remove
>> them from INHERIT
>> 0302:f.write('INHERIT_remove = "%s"\n' %
>> d.getVar('SDK_INHERIT_BLACKLIST', False))
>> Exception: UnboundLocalError: local variable 'uninative_checksum'
>> referenced before assignment
>>
>> ERROR: core-image-minimal-1.0-r0 do_populate_sdk_ext: Function failed:
>> copy_buildsystem
>> ERROR: Logfile of failure stored in:
>> /workdir/krogoth/build/tmp-glibc/work/zynq_soft_z7000_mb_v2-oe-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_populate_sdk_ext.8408
>> ERROR: Task
>> (/workdir/krogoth/openembedded-core/meta/recipes-core/images/core-image-minimal.bb:do_populate_sdk_ext)
>> failed with exit code '1'
>> NOTE: Tasks Summary: Attempted 2214 tasks of which 2210 didn't need to be
>> rerun and 1 failed.
>>
>> Summary: 1 task failed:
>>
>> /workdir/krogoth/openembedded-core/meta/recipes-core/images/core-image-minimal.bb:do_populate_sdk_ext
>> Summary: There were 2 ERROR messages shown, returning a non-zero exit
>> code.
>>
>>
>> The standard SDK builds successfully all the way back from Fido t
[yocto] wic error during creating sdimg
Hi, below error is from wic when creating SD image. I have no clue where error can be. I'm portin mender to orangepi and already asked for support but seems nobody really understand what is going on. Any help appreciated. error log: DEBUG: Executing python function set_image_size DEBUG: Python function set_image_size finished DEBUG: Executing python function extend_recipe_sysroot NOTE: Direct dependencies are ['virtual:native:/home/marek/projects/orangepi_plus/orange-pi-distro/poky/meta/recipes-devtools/dosfstools/dosfstools_4.1.bb:do_populate_sysroot', 'virtual:native:/home/marek/projects/orangepi_plus/orange-pi-distro/poky/meta/recipes-extended/parted/parted_3.2.bb:do_populate_sysroot', 'virtual:native:/home/marek/projects/orangepi_plus/orange-pi-distro/poky/meta/recipes-devtools/rsync/rsync_3.1.2.bb:do_populate_sysroot', '/home/marek/projects/orangepi_plus/orange-pi-distro/poky/meta/recipes-kernel/kmod/depmodwrapper-cross_1.0.bb:do_populate_sysroot', 'virtual:native:/home/marek/projects/orangepi_plus/orange-pi-distro/poky/meta/recipes-devtools/prelink/prelink_git.bb:do_populate_sysroot', 'virtual:native:/home/marek/projects/orangepi_plus/orange-pi-distro/poky/meta/recipes-devtools/fdisk/gptfdisk_1.0.3.bb:do_populate_sysroot', '/home/marek/projects/orangepi_plus/orange-pi-distro/poky/meta/recipes-devtools/mklibs/mklibs-native_0.1.43.bb:do_populate_sysroot', '/home/marek/projects/orangepi_plus/orange-pi-distro/poky/meta/recipes-core/meta/wic-tools.bb:do_populate_sysroot', 'virtual:native:/home/marek/projects/orangepi_plus/orange-pi-distro/poky/meta/recipes-devtools/pseudo/pseudo_1.8.2.bb:do_populate_sysroot', 'virtual:native:/home/marek/projects/orangepi_plus/orange-pi-distro/poky/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb:do_populate_sysroot', '/home/marek/projects/orangepi_plus/orange-pi-distro/poky/meta/recipes-devtools/qemu/qemuwrapper-cross_1.0.bb:do_populate_sysroot', 'virtual:native:/home/marek/projects/orangepi_plus/orange-pi-distro/poky/meta/recipes-devtools/mtools/mtools_4.0.18.bb:do_populate_sysroot', 'virtual:native:/home/marek/projects/orangepi_plus/orange-pi-distro/poky/meta/recipes-devtools/opkg-utils/opkg-utils_0.3.5.bb:do_populate_sysroot', 'virtual:native:/home/marek/projects/orangepi_plus/orange-pi-distro/poky/meta/recipes-devtools/opkg/opkg_0.3.5.bb:do_populate_sysroot', 'virtual:native:/home/marek/projects/orangepi_plus/orange-pi-distro/poky/meta/recipes-devtools/makedevs/makedevs_1.0.1.bb:do_populate_sysroot', '/home/marek/projects/orangepi_plus/orange-pi-distro/poky/meta/recipes-core/glibc/ldconfig-native_2.12.1.bb:do_populate_sysroot', 'virtual:native:/home/marek/projects/orangepi_plus/orange-pi-distro/poky/meta/recipes-extended/pigz/pigz_2.3.4.bb:do_populate_sysroot'] NOTE: Installed into sysroot: ['dosfstools-native', 'parted-native', 'rsync-native', 'gptfdisk-native', 'wic-tools', 'mtools-native', 'acl-native'] NOTE: Skipping as already exists in sysroot: ['depmodwrapper-cross', 'prelink-native', 'mklibs-native', 'pseudo-native', 'update-rc.d-native', 'qemuwrapper-cross', 'opkg-utils-native', 'opkg-native', 'makedevs-native', 'ldconfig-native', 'pigz-native', 'gnu-config-native', 'pkgconfig-native', 'quilt-native', 'autoconf-native', 'xz-native', 'automake-native', 'libtool-native', 'systemd-systemctl-native', 'readline-native', 'util-linux-native', 'texinfo-dummy-native', 'gettext-minimal-native', 'ncurses-native', 'shadow-native', 'popt-native', 'attr-native', 'nss-native', 'elfutils-native', 'binutils-native', 'zlib-native', 'openssl-native', 'debianutils-native', 'qemu-native', 'kmod-native', 'libarchive-native', 'libsolv-native', 'm4-native', 'lzo-native', 'sqlite3-native', 'nspr-native', 'flex-native', 'bison-native', 'cryptodev-linux-native', 'makedepend-native', 'pixman-native', 'libsdl-native', 'glib-2.0-native', 'alsa-lib-native', 'dtc-native', 'gtk-doc-native', 'bzip2-native', 'e2fsprogs-native', 'cmake-native', 'expat-native', 'rpm-native', 'util-macros-native', 'xproto-native', 'libpng-native', 'libx11-native', 'libxext-native', 'libxrandr-native', 'libxrender-native', 'libffi-native', 'gettext-native', 'libpcre-native', 'python3-native', 'curl-native', 'db-native', 'dbus-native', 'file-native', 'xtrans-native', 'inputproto-native', 'xextproto-native', 'kbproto-native', 'libxcb-native', 'randrproto-native', 'renderproto-native', 'libxdmcp-native', 'xcb-proto-native', 'libpthread-stubs-native', 'libxau-native'] DEBUG: Python function extend_recipe_sysroot finished DEBUG: Executing shell function do_image_sdimg + mkdir -p /home/marek/projects/orangepi_plus/orange-pi-distro/build/tmp-glibc/work/orange_pi_pc_plus-oe-linux-gnueabi/opipcplus-minimal/1.0-r0 + mkdir -p /home/marek/projects/orangepi_plus/orange-pi-distro/build/tmp-glibc/work/orange_pi_pc_plus-oe-linux-gnueabi/opipcplus-minimal/1.0-r0/rootfs + rm -rf /home/marek/projects/orangepi_plus/orange-pi-distro/build/tmp-glibc/work/orange_pi_pc_plus-oe-linux-gnueabi/opipcplus-minimal/1.0-r0/data + mkdir -p
Re: [yocto] wic error during creating sdimg
Hi, seems to be caused by empty IMAGE_BOOT_FILES. When added to machine.conf everything works as expected. Sorry for noise. On Thu, Jan 11, 2018 at 8:45 PM, Belisko Marek wrote: > Hi, > > below error is from wic when creating SD image. I have no clue where > error can be. I'm portin mender to orangepi and already asked for > support but seems nobody really understand what is going on. Any help > appreciated. > > error log: > > DEBUG: Executing python function set_image_size > DEBUG: Python function set_image_size finished > DEBUG: Executing python function extend_recipe_sysroot > NOTE: Direct dependencies are > ['virtual:native:/home/marek/projects/orangepi_plus/orange-pi-distro/poky/meta/recipes-devtools/dosfstools/dosfstools_4.1.bb:do_populate_sysroot', > 'virtual:native:/home/marek/projects/orangepi_plus/orange-pi-distro/poky/meta/recipes-extended/parted/parted_3.2.bb:do_populate_sysroot', > 'virtual:native:/home/marek/projects/orangepi_plus/orange-pi-distro/poky/meta/recipes-devtools/rsync/rsync_3.1.2.bb:do_populate_sysroot', > '/home/marek/projects/orangepi_plus/orange-pi-distro/poky/meta/recipes-kernel/kmod/depmodwrapper-cross_1.0.bb:do_populate_sysroot', > 'virtual:native:/home/marek/projects/orangepi_plus/orange-pi-distro/poky/meta/recipes-devtools/prelink/prelink_git.bb:do_populate_sysroot', > 'virtual:native:/home/marek/projects/orangepi_plus/orange-pi-distro/poky/meta/recipes-devtools/fdisk/gptfdisk_1.0.3.bb:do_populate_sysroot', > '/home/marek/projects/orangepi_plus/orange-pi-distro/poky/meta/recipes-devtools/mklibs/mklibs-native_0.1.43.bb:do_populate_sysroot', > '/home/marek/projects/orangepi_plus/orange-pi-distro/poky/meta/recipes-core/meta/wic-tools.bb:do_populate_sysroot', > 'virtual:native:/home/marek/projects/orangepi_plus/orange-pi-distro/poky/meta/recipes-devtools/pseudo/pseudo_1.8.2.bb:do_populate_sysroot', > 'virtual:native:/home/marek/projects/orangepi_plus/orange-pi-distro/poky/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb:do_populate_sysroot', > '/home/marek/projects/orangepi_plus/orange-pi-distro/poky/meta/recipes-devtools/qemu/qemuwrapper-cross_1.0.bb:do_populate_sysroot', > 'virtual:native:/home/marek/projects/orangepi_plus/orange-pi-distro/poky/meta/recipes-devtools/mtools/mtools_4.0.18.bb:do_populate_sysroot', > 'virtual:native:/home/marek/projects/orangepi_plus/orange-pi-distro/poky/meta/recipes-devtools/opkg-utils/opkg-utils_0.3.5.bb:do_populate_sysroot', > 'virtual:native:/home/marek/projects/orangepi_plus/orange-pi-distro/poky/meta/recipes-devtools/opkg/opkg_0.3.5.bb:do_populate_sysroot', > 'virtual:native:/home/marek/projects/orangepi_plus/orange-pi-distro/poky/meta/recipes-devtools/makedevs/makedevs_1.0.1.bb:do_populate_sysroot', > '/home/marek/projects/orangepi_plus/orange-pi-distro/poky/meta/recipes-core/glibc/ldconfig-native_2.12.1.bb:do_populate_sysroot', > 'virtual:native:/home/marek/projects/orangepi_plus/orange-pi-distro/poky/meta/recipes-extended/pigz/pigz_2.3.4.bb:do_populate_sysroot'] > NOTE: Installed into sysroot: ['dosfstools-native', 'parted-native', > 'rsync-native', 'gptfdisk-native', 'wic-tools', 'mtools-native', > 'acl-native'] > NOTE: Skipping as already exists in sysroot: ['depmodwrapper-cross', > 'prelink-native', 'mklibs-native', 'pseudo-native', > 'update-rc.d-native', 'qemuwrapper-cross', 'opkg-utils-native', > 'opkg-native', 'makedevs-native', 'ldconfig-native', 'pigz-native', > 'gnu-config-native', 'pkgconfig-native', 'quilt-native', > 'autoconf-native', 'xz-native', 'automake-native', 'libtool-native', > 'systemd-systemctl-native', 'readline-native', 'util-linux-native', > 'texinfo-dummy-native', 'gettext-minimal-native', 'ncurses-native', > 'shadow-native', 'popt-native', 'attr-native', 'nss-native', > 'elfutils-native', 'binutils-native', 'zlib-native', 'openssl-native', > 'debianutils-native', 'qemu-native', 'kmod-native', > 'libarchive-native', 'libsolv-native', 'm4-native', 'lzo-native', > 'sqlite3-native', 'nspr-native', 'flex-native', 'bison-native', > 'cryptodev-linux-native', 'makedepend-native', 'pixman-native', > 'libsdl-native', 'glib-2.0-native', 'alsa-lib-native', 'dtc-native', > 'gtk-doc-native', 'bzip2-native', 'e2fsprogs-native', 'cmake-native', > 'expat-native', 'rpm-native', 'util-macros-native', 'xproto-native', > 'libpng-native', 'libx11-native', 'libxext-native', > 'libxrandr-native', 'libxrender-native', 'libffi-native', > 'gettext-native', 'libpcre-native', 'python3-native', 'curl-native', > 'db-native', 'dbus-native', 'file-native', 'xtrans-native', > 'inputproto-native', 'xextproto-native', 'kbproto-native', > 'libxcb-native', 'randrproto-native', 'renderproto-native', > 'libxdmcp-native', 'xcb-proto-native', 'libpthread-stubs-native', > 'libxau-native'] > DEBUG: Python function extend_recipe_sysroot finished > DEBUG: Executing shell function do_image_sdimg > + mkdir -p > /home/marek/projects/orangepi_plus/orange-pi-distro/build/tmp-glibc/work/orange_pi_pc_plus-oe-linux-gnueabi/opipcplus-minimal/1.0-r0 > + mkdir
[yocto] [ANNOUNCEMENT] Yocto Project 2.3.3 (pyro 17.0.3) Released
Hello, The latest release of the Yocto Project 2.3.3 (pyro-17.0.3) is now available for download at: http://downloads.yoctoproject.org/releases/yocto/yocto-2.3.3/poky-pyro-17.0.3.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.3.3/poky-pyro-17.0.3.tar.bz2 A gpg signed version of these release notes is available at: http://downloads.yoctoproject.org/releases/yocto/yocto-2.3.3/RELEASENOTES Full pass test report is available at: https://wiki.yoctoproject.org/wiki/WW51_-_2017-12-20-_Full_Test_Cycle_-_2.3.3_rc1 Thank you to everyone for your contributions to this release! Tracy Graydon Yocto Project Build and Release tracy.gray...@intel.com -- yocto-2.3.3 Errata -- Release Name: eclipse-poky-neon-pyro-17.0.3 Branch: pyro Tag: pyro-17.0.3 Hash: 83e0083ef3a71e10039ace7d18057dddc154408b md5: d6720856accbf2352f2af096a623b916 eclipse-poky-neon-pyro-17.0.3.tar.bz2 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.3.3/eclipse-poky-neon-pyro-17.0.3.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.3.3/eclipse-poky-neon-pyro-17.0.3.tar.bz2 Release Name: eclipse-poky-oxygen-pyro-17.0.3 Branch: pyro Tag: pyro-17.0.3 Hash: 126e707a6de212feeaaf093edc170aaa74192ce7 md5: 76fafcbc3e6652056a12de050652143d eclipse-poky-oxygen-pyro-17.0.3.tar.bz2 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.3.3/eclipse-poky-oxygen-pyro-17.0.3.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.3.3/eclipse-poky-oxygen-pyro-17.0.3.tar.bz2 Release Name: meta-qt3-pyro-17.0.3 Branch: pyro Tag: pyro-17.0.3 Hash: f33b73a9563f2dfdfd0ee37b61d65d90197a456f md5: 9fc77e78dda20002c522f4bc17fab3a5 meta-qt3-pyro-17.0.3.tar.bz2 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.3.3/meta-qt3-pyro-17.0.3.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.3.3/meta-qt3-pyro-17.0.3.tar.bz2 Release Name: meta-qt4-pyro-17.0.3 Branch: pyro Tag: pyro-17.0.3 Hash: 88989ae3abe98b30089e7518d3adabe990c40a10 md5: e32fa92d28944161e168ed1c4b4e73cf meta-qt4-pyro-17.0.3.tar.bz2 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.3.3/meta-qt4-pyro-17.0.3.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.3.3/meta-qt4-pyro-17.0.3.tar.bz2 Release Name: poky-pyro-17.0.3 Branch: pyro Tag: pyro-17.0.3 Hash: 022df4653576c72752156bef8fda0e1aa46733d2 md5: e9f90fc73e26ba613a78a755d600029d poky-pyro-17.0.3.tar.bz2 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.3.3/poky-pyro-17.0.3.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.3.3/poky-pyro-17.0.3.tar.bz2 --- Known Issues --- N/A -- Security Fixes -- bluez5: fix out-of-bounds access in SDP server (CVE-2017-1000250) binutls: Security fixes for CVE-2017-9955, CVE-2017-9954, CVE-2017-9756, CVE-2017-9755, CVE-2017-9753, CVE-2017-9752, CVE-2017-9751, CVE-2017-9750, CVE-2017-9749, CVE-2017-9748, CVE-2017-9747, CVE-2017-9746, CVE-2017-9745, CVE-2017-9744, CVE-2017-9742, CVE-2017-9040, CVE-2017-9042, CVE-2017-9039, CVE-2017-9038, CVE-2017-9044, CVE-2017-8421, CVE-2017-8398, CVE-2017-8396, CVE-2017-8397, CVE-2017-8395, CVE-2017-8394, CVE-2017-8393, CVE-2017-7614, CVE-2017-7223 ruby: Security fixed for CVE-2017-14064 curl: Security fix for CVE-2017-1000101 and CVE-2017-1000100 tiff: Security fixes for CVE-2017-7593, CVE-2017-7602, CVE-2017-7601, CVE-2017-7598, CVE-2017-7596, CVE-2017-7595, CVE-2017-7594, CVE-2017-7592, CVE-2016-10270, CVE-2016-10269, CVE-2016-10267, CVE-2016-10266, CVE-2016-10268, CVE-2016-10093, CVE-2016-10271 linuux-yocto/4.1: update to 4.1.43 plus bluetooth CVE-2017-1000251 linux-yocto/4.9: bluetooth: CVE-2017-1000251 linux-yocto/4.4: bluetooth: CVE-2017-1000251 linux-yocto/4.10: bluetooth: CVE-2017-1000251 -- Fixes -- ovmf: Fix build with gcc7 portmaper: checkuri fails. linux-firmware: Remove iwlwifi-8000C-19 SRC_URI diffstat: use HTTP mirror for SRC_URI liburi-perl: update SRC_URI to yoctoproject mirror v86d: take tarball from debian staging.bbclass: handle postinst-useradd-* fixmes runqemu: Add workaround for APIC hang on pre 4.15 kernels on qemux86 cross.bbclass: Remove usage of host flags for cross-compilation archiver: preserve sysroot paths in configured mode archiver: avoid archiving source for glibc-locale archiver.bbclass: adapt do_unpack_and_patch to RSS archiver.bbclass: fix do_ar_original error for matchbox-desktop archiver.bbclass: do not cause kernel rebuilds archiver.bbclass: various fixes for original+diff mode archiver.bbclass: enhance do_ar_recipe task signature archiver: Escape recipe name in regex classes: drop image dependencies on TOPDIR variable image.bbclass: drop initramfs bundle related code local.conf.sample: Weakly set BB_DISKMON_DIRS documenation: Prepared docs for a 2.3.3 point release build-appliance-image: Update to pyro head revision poky: Update version to 2.3.3 cross-localedef-native: Include locale_t.h
[yocto] [ANNOUNCEMENT] Yocto Project 2.4.1 (rocko-18.0.1) Released
Hello, The latest release of the Yocto Project 2.4.1 (rocko-18.0.1) is now available for download at: http://downloads.yoctoproject.org/releases/yocto/yocto-2.4.1/poky-rocko-18.0.1.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.4.1/poky-rocko-18.0.1.tar.bz2 A gpg signed version of these release notes is available at: http://downloads.yoctoproject.org/releases/yocto/yocto-2.4.1/RELEASENOTES Full pass test report is available at: https://wiki.yoctoproject.org/wiki/WW51_-_2017-12-21-_Full_Test_Cycle_-_2.4.1_rc1 Thank you to everyone for your contributions to this release! Tracy Graydon Yocto Project Build and Release tracy.gray...@intel.com -- yocto-2.4.1 Errata -- Release Name: eclipse-poky-neon-rocko-18.0.1 Branch: rocko Tag: rocko-18.0.1 Hash: 83e0083ef3a71e10039ace7d18057dddc154408b md5: e60acf5e3804f4f1c2bf00aa5a185931 eclipse-poky-neon-rocko-18.0.1.tar.bz2 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.4.1/eclipse-poky-neon-rocko-18.0.1.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.4.1/eclipse-poky-neon-rocko-18.0.1.tar.bz2 Release Name: eclipse-poky-oxygen-rocko-18.0.1 Branch: rocko Tag: rocko-18.0.1 Hash: 126e707a6de212feeaaf093edc170aaa74192ce7 md5: 5691fe17276e8c9932b8d384569d07da eclipse-poky-oxygen-rocko-18.0.1.tar.bz2 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.4.1/eclipse-poky-oxygen-rocko-18.0.1.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.4.1/eclipse-poky-oxygen-rocko-18.0.1.tar.bz2 Release Name: meta-qt3-rocko-18.0.1 Branch: rocko Tag: rocko-18.0.1 Hash: f33b73a9563f2dfdfd0ee37b61d65d90197a456f md5: 5cb7e7218605001c06072592b72502f1 meta-qt3-rocko-18.0.1.tar.bz2 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.4.1/meta-qt3-rocko-18.0.1.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.4.1/meta-qt3-rocko-18.0.1.tar.bz2 Release Name: meta-qt4-rocko-18.0.1 Branch: rocko Tag: rocko-18.0.1 Hash: f313dbee2ac3d5fcc9801407947d3cb6cfb90b5d md5: defef8f6b49b5b622f094deb2e47514b meta-qt4-rocko-18.0.1.tar.bz2 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.4.1/meta-qt4-rocko-18.0.1.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.4.1/meta-qt4-rocko-18.0.1.tar.bz2 Release Name: poky-rocko-18.0.1 Branch: rocko Tag: rocko-18.0.1 Hash: c2b641c8a0c4fd71fcb477d788a740c2c26cddce md5: 8790dcd97f8a594987d419eeefadef8b poky-rocko-18.0.1.tar.bz2 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.4.1/poky-rocko-18.0.1.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.4.1/poky-rocko-18.0.1.tar.bz2 --- Known Issues --- N/A -- Security Fixes -- icu: CVE-2017-14952 curl: Security Advisory - curl - CVE-2017-1000254 - Fixes - oeqa/runtime/buildcpio: Use our own mirror for source binutils: Convert SRC_URI and SRCREV to weak defines binutils: update to 2.29.1 acpica: fix build with x32 boost: fix build with x32 and musl runqemu: Add workaround for APIC hang on pre 4.15 kernels on qemux86 glib-2.0: Add python3 modules required by gdbus-codegen lib/oe/patch: add missing import bmap-tools: fix RDEPENDS and update SRC_URI rm_work: remove debugging statements kernel-fitimage: Fix bad image type replacement for aarch64 image-live.bbclass: add MLPREFIX to core-image-minimal-initramfs image-live.bbclass: print warn when initramfs is invalid wic: Fix a path to a psuedo state directory (PSEUDO_LOCALSTATEDIR). waf.bbclass: explicitly pass bindir and libdir if supported kernel.bbclass: Fix do_sizecheck behaviour image_types: btrfs use sparse file creation rm_work: Handle race with -inital tasks linux-yocto/4.12: CQM and kmemleak fixes linux-yocto/4.12: common-pc*: enable X2APIC by default linux-yocto/4.12: update to v.4.12.18 linux-yocto/4.12: bug fixes and feature backports linux-yocto/4.x: configuration updates linux-yocto/4.12: ipv4 stable backport and config changes linux-yocto/4.12: bug fixes and VRF feature addition linux-yocto/4.12: update to v4.12.16 systemd: fix segfault when terminating systemd --test recipetool: create: fix conflict between SRCREV and tag libxslt: use HTTP instead of FTP in SRC_URI ovmf: Fix build failure for PARALLEL_MAKE with no space kernel-yocto: ensure that only a single defconfig is processed kernel-yocto: Stop the build if defconfig is missing kernel-yocto: ensure sccs variable is set when using KBUILD_DEFCONFIG linux-yocto/4.9: update to v4.9.65 linux-yocto/4.12: iwlwifi calltrace fixes and configuration warning cleanups linux-yocto/4.9: update to v4.9.61 rootfs-postcommands.bbclass: ensure that rootfs gets mounted ro connman.inc: do not check IMAGE_FEATURES templates/layer.conf: remove backslash to enable bbappend setting systemd: allow dots in arguments to template units package_manager: force dnf to refresh the cache meta-selftest: fix upstream version checks for devtool test recipes mtd-utils: fix
Re: [yocto] [meta-oic] Question about Iotivity 1.3.0/1 and fixes status
Hi Philippe, On Thu, 11 Jan 2018 at 7:11 PM Philippe Coval < philippe.co...@osg.samsung.com> wrote: > > On 11/01/18 02:30, Chanho Park wrote: > > Hi Philippe, > > > Hi Chanho Park, HNY to you Wish you the same. > > I found you already prepared iotivity 1.3.0, 1.3.1 recipes and fixes > > in your github tree[1]. > > Yes they are still under review, did you test them ? > > Maybe I should resend them, now. Okay. I’ll test them when you resend them. Please CCing me at that time. > > > I wonder why you don’t post them in the meta-oic. > > Well I shared patches to list couple of time: > > https://lists.yoctoproject.org/pipermail/yocto/2017-June/036896.html > https://lists.yoctoproject.org/pipermail/yocto/2017-September/037829.html > https://lists.yoctoproject.org/pipermail/yocto/2017-December/039355.html > > > Do you have a plan to upstream them? > I need reviewer to approve and commit them (@Kishen ?) > or may I do it by my own > since nobody objected on previous changes ? > > Side note, I also simplified a recipe for iotivity master branch > (it now relies on scons install like tizen, debian etc) > > so if it helps I will update devel branch and this page soon: > https://wiki.iotivity.org/wiki/yocto > Okay. I look forward to your results :) Thanks. > > > Best Regards, > BR, Keep in touch your feedback is valuable. Sure. I’ll keep in touch you with my feedback. Best Regards, Chanho Park -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] yocto test framework: problem with bitbake image -c testexport
Hello all,
I just tried to use the yocto testframework as described in [1]. Base is
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=rocko&id=759b36a8de86bfe5355880a76077af47e156701d
As I want to start the tests manually with having the tests exported
(with the goal to fully automate all the steps with tbot [3]), I added
INHERIT += "testimage testexport"
to my local.conf
and start:
bitbake image -c testexport
But bitbaking fails with:
File: '***/meta/classes/testexport.bbclass', lineno: 42, function: do_testexport
0038:do_testexport[depends] += "${TEST_EXPORT_DEPENDS} ${TESTIMAGEDEPENDS}"
0039:do_testexport[lockfiles] += "${TEST_EXPORT_LOCK}"
0040:
0041:python do_testexport() {
*** 0042:testexport_main(d)
0043:}
0044:
0045:def testexport_main(d):
0046:import json
File: '***/meta/classes/testexport.bbclass', lineno: 75, function:
testexport_main
0071:
0072:tc = OERuntimeTestContext(td, logger, target, host_dumper,
0073: image_packages, extract_dir)
0074:
*** 0075:copy_needed_files(d, tc)
0076:
0077:def copy_needed_files(d, tc):
0078:import shutil
0079:import oe.path
File: '***/meta/classes/testexport.bbclass', lineno: 135, function:
copy_needed_files
0131:shutil.copy2(image_manifest, os.path.join(test_data_path,
'manifest'))
0132:shutil.copy2(tdname, os.path.join(test_data_path,
'testdata.json'))
0133:
0134:# Create tar file for common parts of testexport
*** 0135:create_tarball(d, "testexport.tar.gz",
d.getVar("TEST_EXPORT_DIR"))
0136:
0137:# Copy packages needed for runtime testing
0138:package_extraction(d, tc.suites)
0139:test_pkg_dir = d.getVar("TEST_NEEDED_PACKAGES_DIR")
Exception: TypeError: create_tarball() missing 1 required positional argument:
'ar_outdir'
Fixed this (as I am a yocto beginner, only a dummy patch) with patch [4].
May a better fix is here appropriate ... ? If not, I can send a formal
patch to this list?
Going forward ...
With [4] bitbaking finishs, but I see no "tmp/testexport/image" directory, as
described
in [1], instead only a "tmp/testimage/image" exists ... wrong in [1]?
In "tmp/testimage/image" no "runexported.py" ... but a "oe-test" file exists.
Hmm... in "tmp/testimage/image" exists a file "testexport.tar.gz" ...
Extracting this on my machine, from where I have access to the Board I want to
test:
$ ./oe-test runtime --list-tests module
2018-01-12 06:53:20,226 - runtime - INFO - Listing all available test modules:
2018-01-12 06:53:20,226 - runtime - INFO - ping
2018-01-12 06:53:20,226 - runtime - INFO - ssh
2018-01-12 06:53:20,226 - runtime - INFO - connman
2018-01-12 06:53:20,226 - runtime - INFO - date
2018-01-12 06:53:20,226 - runtime - INFO - df
2018-01-12 06:53:20,226 - runtime - INFO - dnf
2018-01-12 06:53:20,226 - runtime - INFO - rpm
2018-01-12 06:53:20,226 - runtime - INFO - scp
2018-01-12 06:53:20,226 - runtime - INFO - xorg
$
$ ./oe-test runtime --target-ip 192.168.3.24 --server-ip 192.168.3.1 --target-type simpleremote
--run-tests ping ssh date df
2018-01-12 06:55:49,874 - runtime - INFO - test_ping (ping.PingTest)
2018-01-12 06:55:49,887 - runtime - INFO - ... ok
2018-01-12 06:55:49,887 - runtime - INFO - test_ssh (ssh.SSHTest)
2018-01-12 06:55:50,599 - runtime - INFO - ... ok
2018-01-12 06:55:50,600 - runtime - INFO - test_date (date.DateTest)
2018-01-12 06:55:53,798 - runtime - INFO - ... ok
2018-01-12 06:55:53,799 - runtime - INFO - test_df (df.DfTest)
2018-01-12 06:55:54,195 - runtime - INFO - ... ok
2018-01-12 06:55:54,195 - runtime - INFO -
--
2018-01-12 06:55:54,195 - runtime - INFO - Ran 4 tests in 4.321s
2018-01-12 06:55:54,195 - runtime - INFO - OK
2018-01-12 06:55:54,196 - runtime - INFO - RESULTS:
2018-01-12 06:55:54,196 - runtime - INFO - RESULTS - date.DateTest.test_date -
Testcase 211: PASSED
2018-01-12 06:55:54,196 - runtime - INFO - RESULTS - df.DfTest.test_df -
Testcase 234: PASSED
2018-01-12 06:55:54,196 - runtime - INFO - RESULTS - ping.PingTest.test_ping -
Testcase 964: PASSED
2018-01-12 06:55:54,196 - runtime - INFO - RESULTS - ssh.SSHTest.test_ssh -
Testcase 224: PASSED
2018-01-12 06:55:54,196 - runtime - INFO - SUMMARY:
2018-01-12 06:55:54,196 - runtime - INFO - runtime () - Ran 4 tests in 4.321s
2018-01-12 06:55:54,196 - runtime - INFO - runtime - OK - All required tests
passed
$
So this seems to work ... Is this correct?
Hmm.. searching for any logs, what this tests do .. I cannot find any log?
No info, which commands are sent, nor any output from them is logged.
The only info I get is above output :-(
Is this correct?
Thanks in advance!
bye,
Heiko
[1]
http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#performing-automated-runtime-testing
[2]
http://www.yoctoproject.org/docs/current/dev-manual/dev
