**** BEGIN LOGGING AT Wed Jan 14 02:59:59 2015
Jan 14 09:37:12 <mago_> how do people generally use bitbake -g output? i find it very difficult to look at, even for the most basic recipes (since OE adds so many dependencies)
Jan 14 09:37:48 <mago_> the graphs grow so big, even with a dot-viewer that allows zooming and panning its more or less useless to visualize the dependencies
Jan 14 09:38:15 <koen> I use vi
Jan 14 09:38:20 <koen> or grep
Jan 14 09:39:47 <mago_> okay, so you don't actually visualize it? i mean, it makes sense to be able to dump the entire dependency tree,.. but perhaps there are other formats to use than dot files (for example JSON), if you can't view it anyways
Jan 14 09:41:33 <koen> no, I only visualize it when encountering an asshole that insists building a distro is easy and dependencies aren't that hard
Jan 14 09:41:51 <mago_> :)
Jan 14 10:05:14 <hrw> ;)
Jan 14 10:30:06 <bluelightning> some day it would be cool to try to print out one of those dependency trees as a wall chart
Jan 14 10:36:15 <mckoan> bluelightning: propbably you'd need the chinese Great Wall though :-D
Jan 14 10:38:41 <LetoThe2nd> mckoan: should only depnd on the dpi
Jan 14 10:39:07 <mckoan> LetoThe2nd: of course ;-)
Jan 14 10:39:50 <mckoan> LetoThe2nd: in case you can use a microfilm viewer :-D
Jan 14 10:40:17 <LetoThe2nd> mckoan: i think there still should be one left here in my wall cab... let me take a look ;)
Jan 14 10:49:39 <kimo_> hi all, Im looking for a thrift recipe, does anyone have tried to cross-compile it for ARM?
Jan 14 10:58:53 <mago_> bluelightning: maybe something you can bring to FOSDEM ;-) a bitbake dependency graph rollup
Jan 14 10:59:05 <bluelightning> mago_: could be :)
Jan 14 12:42:24 <Crofton|work> https://fosdem.org/2015/schedule/event/starting_yocto/
Jan 14 12:46:07 <koen> *sigh*
Jan 14 12:46:15 <koen> I suspect he means 'OE'
Jan 14 13:04:53 <mago_> i think it sounds interesting
Jan 14 13:19:53 <Crofton|work> mago_, it is just getting annoying with people using different words to mean the same thing
Jan 14 13:20:43 <mago_> yeh, i know.. i was very confused with yocto, poky, openembedded, bitbake and all when i joined the community
Jan 14 13:21:14 <Crofton|work> I just make a sign for the embedded room
Jan 14 13:21:23 <Crofton|work> OpenEmbedded is the build system
Jan 14 13:21:33 <Crofton|work> Poky is the reference distribution
Jan 14 13:21:38 <Crofton|work> Yocto is the Project
Jan 14 13:22:14 <Crofton|work> Hmm, I should make stickers
Jan 14 13:22:19 <mago_> =)
Jan 14 13:22:43 <bencoh> bitbake's missing in your list :>
Jan 14 13:23:27 <mago_> To me, yocto is all the marketing & organisational "stuff" of oe.. 
Jan 14 13:23:44 <Crofton|work> that is more accurate
Jan 14 13:24:19 <Crofton|work> we've always been a bit squishy on bitbake being part of the build system or a general purpose tool
Jan 14 13:24:38 <koen> replace 'yocto' with 'github' or 'gnu' to see if you're using the right term
Jan 14 13:24:53 <mago_> i've tried to use bitbake without openembedded once. it was very difficult ;-)
Jan 14 13:24:54 <koen> 'my board runs github!!!one!!'
Jan 14 13:30:25 <LetoThe2nd> koen: oh yours too?
Jan 14 13:35:29 <RP> If anyone sees ENOENT issues with bitbake master, a fix just got pushed
Jan 14 13:44:56 <Crofton|work> No Ent's?
Jan 14 13:45:04 <Crofton|work> I liked the ents.
Jan 14 13:51:52 <LetoThe2nd> ho-ho-hum-hum.
Jan 14 13:53:00 <Crofton|work> Arg "Yocto Linux build system"
Jan 14 14:22:34 <koen> Crofton|work: read the intel edison materials
Jan 14 14:22:43 <Crofton|work> I have
Jan 14 15:15:20 <dgeiger> Hmmm - has anyone here looked at building a more recent release of python 2.7.x in OE before?
Jan 14 15:20:35 <Crofton|work> what is more recent?
Jan 14 15:39:35 <bluelightning> dgeiger: as it happens one of my colleagues is working on it right now
Jan 14 15:40:01 <bluelightning> dgeiger: https://bugzilla.yoctoproject.org/show_bug.cgi?id=7059
Jan 14 15:42:22 <dgeiger> bluelightning: Awesome news for me - thanks!
Jan 14 15:45:23 <Crofton|work> dgeiger, what do you need?
Jan 14 15:45:29 <Crofton|work> from pyton
Jan 14 15:46:26 <dgeiger> Crofton|work: I have some code that I've discovered has some issues with v2.7.3, but 'magically' works with 2.7.8
Jan 14 15:46:36 <Crofton|work> lovely :)
Jan 14 15:47:06 <dgeiger> It looks like somewhere in between those two versions they may have made garbage collections less conservative, and therefor resolved a resource leak I've finding
Jan 14 17:13:10 <awozniak> in oe-core, where is the ARCHITECTURE typically defined?
Jan 14 17:28:53 <jaeckel> when I'm building valgrind, and I add the valgrind-dbg package, there seems to be a file missing in the output files generated
Jan 14 17:29:12 <jaeckel> does someone know what happens to coregrind/pub_core_dispatch_asm.h ?
Jan 14 17:36:23 <jaeckel> oh, there seem to be more missing
Jan 14 17:36:30 <jaeckel> that was just the first I saw
Jan 14 17:38:47 <bluelightning> awozniak: the machine conf file pointed to by MACHINE usually pulls in a tune include file, and the tuning defines all of the architecture-related variable values
Jan 14 17:39:12 <awozniak> thx bluelightning
Jan 15 01:44:07 <gabrbedd> Is there a way to override the BBFILE_PRIORITY_<layername> of a layer without actually modifying the layer?
**** ENDING LOGGING AT Thu Jan 15 02:59:59 2015