**** BEGIN LOGGING AT Mon Sep 01 02:59:58 2014 Sep 01 10:32:10 morning all Sep 01 10:39:57 JaMa: any opinions on the glibc change? Sep 01 10:47:43 RP: I haven't included it in my world builds, because I'll be offline for few weeks starting tomorrow Sep 01 10:47:55 RP: so no strong opinion from me Sep 01 10:48:42 JaMa: its rather late (too late?) but I am leaning towards being adventurous and taking it... Sep 01 10:51:19 we'll also have few extra weeks to fix meta-oe recipes if needed (even after oe-core freeze) so I'm not against it too Sep 01 11:58:42 RP: hi. Back to the gcc sysroot thingie... Sep 01 11:59:26 /arm-oe-linux-gnueabi-klcc: unknown option: --sysroot=/oe/oe-core/build/tmp-eglibc/sysroots/collie Sep 01 11:59:30 :/ Sep 01 11:59:52 do you think I can workaround with -isystem ? Sep 01 12:07:52 ant_work: I know nothing about what klcc is doing Sep 01 12:08:48 I have only a vague idea... http://git.kernel.org/cgit/libs/klibc/klibc.git/tree/klcc/klcc.in Sep 01 12:09:20 long ago woglinde added isystem...I don't know how easy it could be to add --sysroot Sep 01 12:10:15 otherwise the solution is to avoid multimachine builds Sep 01 12:16:20 ant_work: at a quick glance, it shouldn't be hard to add support to that script Sep 01 12:17:56 ant_work: at a guess, copy the section at line 203 but alter to make it use --sysroot Sep 01 12:20:27 ah,m ok, I was perplexed by the two dashes Sep 01 12:23:27 I'll let you know, thanks Sep 01 16:30:36 JaMa: thanks for picking qtwebengine to meta-qt5! Sep 01 18:33:38 I removed my DEPLOY_DIR because I was going to move it under a different drive. How do I for a rebuild of this directory? Sep 01 18:35:10 I was thinking that 'bitbake myimage' would detect that the files were gone and rebuild all the necessary stuff but it does not. Sep 01 19:08:10 JaMa: what is "common-x86" ? Sep 01 19:10:29 dv__: qemux86 and qemux86-64 Sep 01 19:10:52 http://www.openembedded.org/wiki/Bitbake_World_Status#Failed_tasks_2014-09-01 <- chromium doesnt fail for qemux86 , but for common-x86 Sep 01 19:11:14 so there is some difference Sep 01 19:13:25 it means that it fails for both Sep 01 19:13:57 ok. and it fails only when gold is used. correct? Sep 01 19:14:26 it failed when I've tried to disable gold for it (and keep it enabled for rest of system) Sep 01 19:15:35 thats what I meant. you built the system with gold. Sep 01 19:15:50 because in qemux86 builds without gold , it didnt fail for me Sep 01 19:16:18 I actually overlooked that flag of yours.. I am rebuilding with gold now Sep 01 19:17:09 I might have a workaround for this problem. nothing pretty though, but it works. comes originally from tizen. there is a GYP flag to make it not fail when these sqlite warnings occur Sep 01 20:23:16 hello does anybody know how to configure the build of an image to use bash... etc instead of busybox ? Sep 01 20:31:31 just include the packages you need (bash, coreutils/linux-utils/or-some-other-package-I-forgot :) Sep 01 20:34:10 bencoh: there is no meta-package which substitutes busybox or a simple configuration switch ? Sep 01 20:37:36 hm, I dunno Sep 01 20:38:12 bencoh: ok, thank you Sep 01 20:58:55 nschle85: there is packagegroup-core-full-cmdline Sep 01 20:59:33 but that only adds the replacements, it won't actually stop busybox from being included in your image Sep 01 21:01:23 bluelightning: can i remove the busybox via local.conf or must i modify the image receipe ? Sep 01 21:03:07 well, busybox is usually brought in via packagegroup-core-boot, and there's not an easy way to exclude it from there at the moment Sep 01 21:03:29 you could of course not include packagegroup-core-boot in your image (or replace it with a modified packagegroup) Sep 01 21:03:44 honestly at this point I'd say you should definitely have your own image recipe Sep 01 21:04:42 bluelightning: thank you, now ill try... Sep 01 21:41:01 obi Sep 01 21:57:39 RP: seems --sysroot is being injected properly ;) **** ENDING LOGGING AT Tue Sep 02 02:59:59 2014