**** BEGIN LOGGING AT Mon Oct 27 03:00:01 2014 Oct 27 05:42:58 hi, i took a quick look at the bsp page, can't find a specific galileo bsp. Is any of the Intel-core2 compatible with galileo board? Oct 27 08:01:41 Good morning all Oct 27 08:13:05 good morning Oct 27 08:43:49 halstead: have you seen the autobuilder failures? Oct 27 08:50:30 In dora release gstreamer-0.10.36 is built by default. How do I select building with gstreamer1.0 ? Oct 27 09:06:09 Compiler Warnings are nicely visible in the do_compile logs, is there any tool to create statistics or process these automatically to notify persons about these - or maybe even track changes like new warnings since last build and freak out on them? Oct 27 09:41:30 irontia: some time ago I wrote a script to parse gcc output for warnings and associate it with authors using `git blame'. it was not connected with yocto by any means, but was pretty useful. unfortunately, the script was lost on my old PC. Oct 27 10:09:20 RP: hi, I am trying to use meta-mingw, do you have any document (link) explaining how to install and use it on a Win machine once I get the meta-toolchain.bz2? Oct 27 10:15:13 lexszero: that sounds quite like something usefull. Sad that you lost it. Oct 27 10:42:22 mckoan: not really, no, sorry Oct 27 10:54:53 RP: but you ever used it on a Win PC ? Oct 27 11:25:43 mckoan: I wrote the code and yes, I did test it :) Oct 27 11:26:34 mckoan: basically you extract the tools onto a windows system and then you can run gcc and friends to compile code as you would on linux Oct 27 11:28:02 mckoan: the difference is there is no environment script as there is on Linux, we'd don't have that piece as yet Oct 27 11:28:22 someone with more windows skills than me would need to do that if needed Oct 27 11:28:49 RP: thank you Oct 27 11:41:21 c **** BEGIN LOGGING AT Mon Oct 27 12:03:18 2014 Oct 27 12:08:37 RP, I just looked. I think I made some incorrect choices when I triggered the dora build. Oct 27 12:09:12 halstead: how did that break the checkout with those move failures though? Oct 27 12:11:34 RP, I don't know. I guess I haven't looked closely enough yet. Just woke up. Oct 27 12:13:05 halstead: You do seem to be up early! :) Oct 27 12:13:34 It looks like it's a problem with centos7-a especially. Oct 27 12:31:18 * fray successfully made it back to North America.. Oct 27 12:54:03 RP: who is in charge of backports for dizzy? Oct 27 12:54:39 halstead: yes Oct 27 12:54:56 otavio: a stable maintainer isn't sorted out yet Oct 27 12:58:40 how many releases are we supporting at once? Oct 27 12:58:45 oe-core wise Oct 27 14:07:05 hello, I want to create a custom bsp for Beagleboneblack Oct 27 14:08:54 I've created the bsp for beaglebone using "yocto-bsp create" tool, it references the beagleboard in myboneblack.conf, after build it fails to boot. Oct 27 14:10:47 vishnu: yes that's a known issue, could you try replacing those beagleboard references with beaglebone? Oct 27 14:11:11 Crofton|work: I believe it's just the last two normally Oct 27 14:11:24 that's what I thought Oct 27 14:12:12 ok, Is it a limitation that wecan create only one bsp per arch? Oct 27 14:12:36 like beagleboard for ARM. Oct 27 14:13:24 that seems odd Oct 27 14:13:25 vishnu: no, not that I'm aware of... as far as I know this was just a mistake Oct 27 14:14:59 beagleboard is hardcoded in below file /poky/scripts/lib/bsp/substrate/target/arch/arm/conf/machine/{{=machine}}.conf Oct 27 14:15:49 "yocto-bsp create custombspname arm" uses this file to create bsp. Oct 27 14:54:45 good morning Oct 27 15:24:55 what does PRIVATE_LIBS do in package.bbclass? Oct 27 15:38:35 j8: http://www.yoctoproject.org/docs/1.7/ref-manual/ref-manual.html#var-PRIVATE_LIBS Oct 27 15:38:51 (I think we just added that to the manual for this upcoming release) Oct 27 15:39:03 the variable itself has been supported for a while though Oct 27 15:41:04 bluelightning: so that's why i couldn't find it :) Oct 27 15:41:40 indeed... we're slowly chipping away at the (now fairly small) list of undocumented variables Oct 27 16:16:24 Good morning everyone, if I am using systemd, should I still use ifupdown tools? Or is networkd the new way to go? Oct 27 16:21:50 adam_: we currently disable networkd by default I believe Oct 27 16:39:53 bluelightning: Not ready for prime time? Oct 27 16:40:20 bluelightning: ifup is not working for me on 3.17 kernel - it works great on 3.6. So I am trying to figure out my path forward. Oct 27 16:44:16 adam_: AIUI we didn't enable it because it isn't mature and needs further integration which we haven't done yet Oct 27 16:44:24 (systemd-networkd that is) Oct 27 16:59:48 bluelightning: got it - thanks. Do you mind giving me a little more details on its maturity? Oct 27 17:21:35 adam_: I've not been closely involved with it to be honest Oct 27 17:21:53 when rburton is around (he's not currently) perhaps he could advise Oct 27 17:22:33 I'm working to enable selinux support in one of our (working, poky 1.3) older trees prior to porting to our latest (not yet working, poky 1.6) development tree. I'm trying to call the selinux setfiles command in the image command, but it is failing with a not supported error. Oct 27 17:22:53 setfiles get context on /home/michael_e_brown/13g_selinux/build-yocto-sh4/tmp/work/idrac8-poky-linux/idrac-image Oct 27 17:22:53 -1.0.0-r0.0/rootfs/media/mmc1 failed: 'Operation not supported' Oct 27 17:23:10 I thought that pseudo would take care of this. Oct 27 17:25:16 bluelightning: kk thanks! **** ENDING LOGGING AT Tue Oct 28 03:00:00 2014