**** BEGIN LOGGING AT Sun Aug 30 02:59:58 2015 Aug 30 13:53:23 darn, those sneaky meta-fsl-arm people! Aug 30 13:54:12 hidden deep within the GPU Vivante driver recipe, there's a cryptic comment Aug 30 13:54:30 about library dependencies that are not part of the recipe itself Aug 30 13:55:10 so of course bitbake doesn't complain about missing dependencies, but the entire system crashes real hard on boot, kernel just stops! Aug 30 13:55:47 and now it works perfectly after adding those x11 libs it required. Aug 30 13:56:08 oh well, just another day wasted :) Aug 30 14:13:43 be sure to email them .... Aug 30 14:14:28 Hi, what do you mean by oe-init-build-env-memres ? what do you mean by memory-resident BitBake server ? Aug 30 14:14:51 all the files are downloaded to a ramfs ? Aug 30 14:15:41 the documentation it's clear about oe-init-build-env-memres Aug 30 14:15:48 the documentation it's NOT clear about oe-init-build-env-memres Aug 30 14:16:02 can anyone help me? Aug 30 14:33:26 ignore it unless you know you need it? Aug 30 14:33:30 I've never used it Aug 30 14:33:59 ok Aug 30 14:43:14 tanure: memres means the bitbake UI and server are started independently, which means it doesn't re-parse / pull from cache every time you run a bitbake command, they just talk to the persistent running bitbake server process Aug 30 14:43:21 but as Crofton|work says, you probably don't need it Aug 30 14:48:02 thanks Aug 30 14:48:45 "memres means the bitbake UI and server are started independently, which means it doesn't re-parse / pull from cache every time you run a bitbake command" should be on the documentation Aug 30 15:27:21 memory-resident bitbake server is an accurate description. it says nothing about the rootfs or the target, only the behavior of bitbake itself Aug 30 15:27:28 but yes, more detail would be useful Aug 31 00:44:12 I am using yocto fido, but require an update version of alsa (1.0.29), which is the version on master. However I am having some issues with the master build so I would like to stay with fido for now. Is there a simple way in which I can specify the version of alsa in my local.conf to be 1.0.29? Aug 31 00:45:12 not if it's on another branch... Aug 31 00:45:25 at least none that i know of Aug 31 00:48:58 OK. I tried to build master but got this error:file://GNU_SOURCE_definition.patch'. Unable to fetch URL from any source. Any ideas? Aug 31 00:50:01 it's a local file... do a find on it? Aug 31 00:50:28 maybe pull on master again... Aug 31 00:52:15 then run around the block a couple times a do it again... Aug 31 00:53:52 Will investigate a little later maybe. I think I will use fido and build alsa-1.0.29 separately. Should get me to where I want to be. Thanks a lot for your help nerdboy. I really appreciate that there are people on these IRC's that are responsive to people who have no idea (me). Still have a lot to get my head around but atleast I am getting somewhere now.. Aug 31 00:56:31 more hands-on, more docs Aug 31 00:56:36 that's about all i got Aug 31 00:57:35 it's a lot of stuff to go through between the docs and the training stuff Aug 31 00:58:35 one thing coming up next ELC, you could sign up for the developer day thing and get a real crash course Aug 31 00:58:50 comes with hardware even Aug 31 01:01:14 I think one of the issues in this space is the cross-over of different projects/or whatever. Poky, yocto, angstrom, arago and then meta-yocto-bsp, meta-ti, meta-openembedded, and then hob, toaster, bitbake etc. Understanding the interactions and distinctions within these categories is not trivial. Aug 31 01:01:56 well, angstrom is not in your bb_layers Aug 31 01:02:15 there are talks for that stuff too Aug 31 01:02:48 buildroot vs. oe, tizen, yada yada **** ENDING LOGGING AT Mon Aug 31 02:59:59 2015