**** BEGIN LOGGING AT Sun Feb 24 02:59:56 2019 Feb 24 03:58:32 what is the simplest and fast bootable image that can be tested with qemu-arm Feb 24 05:41:22 New news from stackoverflow: How can I install OpenCV on Yocto linux version Feb 24 06:09:28 i have the same question Feb 24 06:17:46 yocti: hello Feb 24 06:17:47 black_13: Error: "hello" is not a valid command. Feb 24 08:48:27 black_13: I'm using a modified version of https://github.com/gmacario/easy-build/blob/master/build-yocto/Dockerfile Feb 24 12:47:31 nayfe: how do you bring up and down the container. Feb 24 12:48:07 and do you run provisioning script Feb 24 12:48:22 I have a jenkins job that creates docker, then I can use it when I launch jenkins builds Feb 24 12:51:06 basically first one do "docker built -t ." and "docker push " Feb 24 12:53:19 The build job uses modified setup-environment script from freescale BSP (https://github.com/Freescale/fsl-community-bsp-base/blob/thud/setup-environment) Feb 24 12:54:59 black_13: i'm not sure i'm clear enough :) Feb 24 13:14:56 sorry i read this with sleep still in my eyes Feb 24 16:26:45 you can use socket activation for docker so it launches when its needed and use yoe distro, it will automatically download docker image and provision it and launch it as needed Feb 24 18:47:41 Hi Feb 24 18:47:54 I have a problem with /var/lib in do_rootfs Feb 24 18:48:13 file /var/lib conflicts between attempted installs of xxx and yyy Feb 24 18:48:49 at first I was thinking it had to do with acl, but they seem the same 755 Feb 24 18:50:40 fenrig_: did you check uid/gid? Feb 24 18:51:05 let me check again to be sure Feb 24 18:53:30 the same Feb 24 18:54:27 the recipe base-files has /var/lib and my other recipe generated /var/lib// Feb 24 18:54:33 could it be due to that? Feb 24 18:54:44 though that seems kind odd to me :/ Feb 24 18:55:01 No, that's usually not a problem. The archive needs to contain that folder anyway. Feb 24 18:55:50 what else ??? Feb 24 18:57:34 they have different creation dates :/ Feb 24 18:57:43 but that also shouldnt be a problem Feb 24 18:58:18 btw looking in build/tmp/work Feb 24 18:58:30 in the respective image directory of those conflicting components Feb 24 19:00:57 yeah, that's where I'd look, too. Feb 24 19:01:38 damn :P then there is no hope Feb 24 19:11:05 can I do something in the recipe to force my way through? Feb 24 19:20:30 Hi, i am new to the yocto project and struggling a bit with adding OpenCV to my build - CORE_IMAGE_EXTRA_INSTALL += “opencv” Feb 24 19:21:47 I get some error messages related to dependency missmatch, with the hint to to add '--allowerasing'. Currently i feel a bit stupid because i do not where i could add it. Maybe someone of you can help me out :) Feb 24 19:40:56 neverpanic: forced my way through by installing to /opt/lib instead of /var/lib Feb 24 20:21:32 khem: trying rpi3 on sumo has some failures in bison-native and cross-localedef-native Feb 24 20:21:44 should i just switch to thud? Feb 24 20:46:32 RP: quick question about quite old commit http://git.openembedded.org/openembedded-core/commit/?id=1392f959cb8cd50b5a4492899e54f3ed68ef56d7 do you remember why package_get_auto_pr was needed also for do_install? Feb 24 20:49:06 RP: I'm working on #12937 and there I'm adding do_deploy_links task which also needs to expand AUTOINC, but in this case the task hash of do_deploy and do_deploy_links is different, so it gets different number from PRserv and PKGR in KERNEL_IMAGE_BASE_NAME as different value in these 2 tasks (so do_deploy_links cannot find artifact created in do_deploy if the naming contains PKGR). Feb 24 20:55:45 RP: and I think the same issue would be if do_install uses any filename with PKGR and do_deploy tries to deploy it (but it doesn't because do_install installs only with e.g. ${KERNEL_IMAGEDEST}/$imageType-${KERNEL_VERSION} which doesn't include PKGR) Feb 24 21:53:56 nerdboy it should be working if you use one of supported distros for sumo Feb 24 21:54:01 and not a rolling one Feb 24 22:00:24 that's kinda what i thought... a musl build should be somewhat less susceptible to that? Feb 24 22:45:39 yeah since no locales Feb 24 23:37:20 runqemu - ERROR - ~/poky_simple_qemu/build/tmp/deploy/images/qemuarm not a directory valid DEPLOY_DIR_IMAGE Feb 25 00:19:11 what is the settings for the local.conf to allow me to use the qemu arm test Feb 25 00:24:27 black_13: https://github.com/YoeDistro/yoe-distro/blob/master/conf/local.conf.sample Feb 25 00:24:40 copy it into local.conf Feb 25 00:24:55 and make changes as needed Feb 25 00:27:51 did you follow the readme ? Feb 25 00:28:39 . ./qemuarm-envsetup.sh && bitbake yoe-simple-image then execute runqemu nographic Feb 25 00:33:31 khem: thud doesn't fail on either bison or cross-localedef Feb 25 00:33:55 * for me on unsupported gentoo build host Feb 25 00:35:18 i probably don't update frequently enough but i'm pretty much always on ~hardened or ~musl-hardened profile Feb 25 00:36:23 nerdboy: yeah thud is recent enough Feb 25 00:36:49 usually glibc (uninative) is an issue for rolling distros Feb 25 00:37:36 yeah i don't remember the shim being installed until (relatively) recently Feb 25 00:37:50 branch-wise recently... Feb 25 02:08:46 khem: i had to step away and make dinner **** ENDING LOGGING AT Mon Feb 25 02:59:57 2019