**** BEGIN LOGGING AT Sun Sep 20 02:59:58 2015 Sep 20 15:50:26 what should the "Sysroot Location" for the eclipse plugin be in the non-prebuilt/system-derived case? Sep 20 15:50:39 i.e., after e.g. bitbake core-image-sato Sep 20 15:57:08 khem`: We are trying to improve the QA tests on OE-Core :) Sep 20 16:32:46 RP: thats good to know Sep 20 16:33:26 RP: btw. I have a patch to replace xz with pxz improves xz image generation time Sep 20 16:33:54 https://github.com/kraj/openembedded-core/commit/360ced50b724cd6648cf27da607c7f7d78918a86 Sep 20 16:34:37 we should default to using pigz for .gz iamages Sep 20 16:34:40 as well Sep 20 16:41:51 nice Sep 20 16:42:45 that's an impressive time improvement Sep 20 17:06:04 kergoth: yeah these images are humungous Sep 20 17:55:57 how can one figure out what is pulling mesa? Sep 20 18:15:10 KvH_: there is a "bitbake -g" flag which will export dependencies as a .dot (graphviz) file Sep 20 18:35:29 as a quick test, i'm trying to get eclipse set up with the yocto plugin and an x86 core-image-sato. i have "Sysroot Location:" set to /build/tmp/sysroots/qemux86 in the project properties. running qemu via 'run->external tools->qemu_i586-poky-linux' errors out with "Error: /build/tmp/sysroots/qemux86/../qemux86.pseudo_state does not exist." Sep 20 18:35:42 "did you create the export directory using runqemu-extract-sdk?" Sep 20 18:36:10 manually creating that directory (as empty) makes it proceed a bit further, but i'm not sure if it's the right thing to do Sep 20 18:36:23 runqemu-extract-sdk doesn't seem like it'd be relevant here :/ Sep 20 18:43:23 Tarnyko: thanks. Sep 20 18:46:00 is there a way to tell bitbake not to use any chached data and just start from beginning? Sep 20 18:57:34 okay, looks like you have to run runqemu-extract-sdk even in that case on the rootfs tarball, for whatever reason, and use that... Sep 20 19:08:39 but now the build is broken instead Sep 20 19:16:57 does anyone know other contacts of "aport"? Sep 20 19:27:29 mh, i accidentially called bitbake -f, but this is not "force". Now there is a message about a taint hash every time i start bitbake Sep 20 19:27:47 how to get away this "tainting"? Sep 20 19:30:28 ah, nevermind **** ENDING LOGGING AT Mon Sep 21 02:59:59 2015