**** BEGIN LOGGING AT Mon Jun 17 02:59:58 2013
Jun 17 07:35:51 <silvio_l_> morning all
Jun 17 07:41:04 <silviof> morning silvio_l_ and all
Jun 17 07:41:25 <silvio_l_> hi silviof ,all
Jun 17 08:24:44 <bluelightning> morning all
Jun 17 08:30:07 <ant_work> bluelightning: gm
Jun 17 08:30:20 <bluelightning> hi ant_work
Jun 17 08:31:25 <ant_work> maybe I missed it, is there any further cleaning foresee for meta-oe? Janitors?
Jun 17 08:37:53 <bluelightning> ant_work: do you mean removal of bbappends/overlayed recipes? or upgrading/cleaning of older recipes?
Jun 17 08:44:32 <ant_work> I was just browsing meta-oe and am under the impression many recipes are just adding c++ bindings
Jun 17 08:45:49 <bluelightning> ant_work: examples?
Jun 17 08:46:53 <ant_work> I started in recipes-core
Jun 17 08:51:21 <ant_work> it will be painful but we'll have to split even more
Jun 17 08:54:25 <jackmitchell> err, as of a pull of master this morning; (bitbake, oe-core, 3rd party recipes) - sourcing oe-init-build-env causes my terminal to crash; is anyone else experiencing this?
Jun 17 08:55:21 <ant_work> maybe it's just me but it would seem adviseable to remove meta-oe and create many sibling layers under meta-openembedded
Jun 17 08:55:39 <ant_work> wasn't this already agreed?
Jun 17 08:57:08 <silvio_l_> hi bluelightning , ant_work 
Jun 17 08:58:26 <ant_work> jackmitchell: I pulled 10-12 hours ago and all was normal then
Jun 17 08:58:43 <bluelightning> ant_work: not that I know of... I'd be in favour of further splits myself provided that we can make them in logical places, cross-layer dependencies don't become an issue and we can find maintainers
Jun 17 08:59:17 <jackmitchell> what is the best way to debug a script which crashes the terminal? I don't even know where to really start with this
Jun 17 08:59:57 <bluelightning> jackmitchell: well, if your terminal crashes it's definitely a bug in the terminal
Jun 17 09:00:11 <jackmitchell> ah, ok
Jun 17 09:00:13 <bluelightning> jackmitchell: however git bisect is probably the easiest way to find out what's triggering the crash
Jun 17 09:00:27 <jackmitchell> yeah I just reverted a few bitbake commits and that didn't fix anything
Jun 17 09:00:31 <bluelightning> especially since the test is an easy one
Jun 17 09:00:43 <jackmitchell> I'll tyr with xterm
Jun 17 09:01:14 <jackmitchell> nope, crashes xterm too, or I suppose it could be calling quit/exit somewhere?
Jun 17 09:01:35 <bluelightning> er... ?!
Jun 17 09:01:44 <ant_work> bluelightning: recipes-multimedia and recipes-navigation seem really low hanging fruits
Jun 17 09:01:45 <bluelightning> FWIW, it works here
Jun 17 09:01:58 <jackmitchell> heh; exactly my thoughts when it happened this morning; I'll try a bisect on oe-core
Jun 17 09:02:06 <ant_work> and then all the C++ bindings in one layer maybe
Jun 17 09:02:09 <bluelightning> ant_work: right, many of the recipes in recipes-multimedia should move to meta-multimedia which we already have
Jun 17 09:02:43 <bluelightning> ant_work: I think that would be less useful since language binding usage will be spread wider
Jun 17 09:03:03 <ant_work> meta-extra-bindings ;)
Jun 17 09:04:16 <ant_work> afais th e.bbappend on top of oe-core do add some functionality neglected there.. 
Jun 17 09:04:47 <jackmitchell> bingo: scripts/oe-buildenv-internal bitbake: Migrate python version checks
Jun 17 09:04:52 <bluelightning> I wonder if *mm could move to meta-gnome
Jun 17 09:05:40 <ant_work> then we have new turbo jpeg but older sqlite...how that?
Jun 17 09:05:45 <bluelightning> ant_work: khem is supposed to be sorting out the busybox bbappend
Jun 17 09:05:53 <bluelightning> ant_work: that's sqlite2
Jun 17 09:06:03 <ant_work> incompatible?
Jun 17 09:06:05 <bluelightning> yes
Jun 17 09:06:15 <ant_work> I see
Jun 17 09:06:24 <bluelightning> re libjpeg-turbo, not sure... it's a fork AIUI
Jun 17 09:06:26 <ant_work> meta-legacy
Jun 17 09:06:53 <ant_work> anyhow you get all the same stuff cloning meta-openembedded
Jun 17 09:07:17 <ant_work> so for the user shouldn't change much
Jun 17 09:08:34 <ant_work> it would be nice if we'd make meta-oe slim soon, profiting of the slow summer's commit rate
Jun 17 09:20:13 <mistry> hi, can anybody please show me how to debug nand issues in embedded linux? i'm trying to port a nand flash. nand is new. there is some issue in the kernel i built. i wanna narrow it down.
Jun 17 09:21:09 <ant_work> mistry: #mtd
Jun 17 09:21:36 <ant_work> what do you mean for debug? kernel rebuilding?
Jun 17 09:21:38 <mistry> oh!! theres a seperate channal.. thanks
Jun 17 09:21:56 <ant_work> yes, not on freenode
Jun 17 09:22:07 <mistry> #mtd seems empty
Jun 17 09:22:25 <mistry> @ant_work what network then?
Jun 17 09:22:51 <ant_work> irc.oftc.net
Jun 17 09:23:23 <mistry> ant_work: yes. i want to know what exact parameter i missed while enabling nand support in linux
Jun 17 09:25:00 <ant_work> depends on which hardware and sort of nand
Jun 17 09:26:43 <mistry> it seems like a really lack a lot of knowledge about nand. does anyone have a link to good article or something on nand
Jun 17 09:28:58 <ant_work> the site of reference is http://www.linux-mtd.infradead.org/faq/nand.html
Jun 17 09:29:13 <bluelightning> jackmitchell: ah, figured out the problem - the version check code was cut-and-pasted and contains "exit 1" which will exit the calling shell when sourced
Jun 17 09:29:44 <jackmitchell> bluelightning: ok, what should it be, return?
Jun 17 09:29:59 <bluelightning> jackmitchell: not sure, I think RP is working on it
Jun 17 09:30:11 <jackmitchell> ok; I'll hold tight
Jun 17 09:30:44 <bluelightning> jackmitchell: in the mean time I think you'll need to actually set up a python 2.x environment since that is why it's exiting
Jun 17 09:31:13 <jackmitchell> yeah that was what I figured; I don't mind being a couple of commits behind till it gets sorted
Jun 17 09:32:17 <mistry> thnx ant_work
Jun 17 09:32:19 <ant_work> I pulled i the hope to avoid the double bitbake run ;)
Jun 17 09:41:29 <RP> jackmitchell: I pushed a fix
Jun 17 09:42:00 <jackmitchell> RP: cheers
Jun 17 09:56:14 <ant_work> RP: while you hang around, what's the meta-filesystems plan? Is it for soon? Should I really commit my cramfs-native in BSP layer?
Jun 17 10:02:48 <RP> ant_work: I don't think anyone suggested it for a BSP layer
Jun 17 10:03:14 <RP> ant_work: the question does remain, does cramfs really belong in the core. We've rejected other filesystem pieces...
Jun 17 10:03:49 <ant_work> RP: will meta-filesystems reside in meta-openembedded on oe-core repository in your plans?
Jun 17 10:03:58 <ant_work> s/on/or/
Jun 17 10:05:18 <RP> ant_work: meta-oe
Jun 17 10:05:34 <ant_work> ouch
Jun 17 10:07:10 <ant_work> we were just talking about making meta-oe disappear  ;)
Jun 17 10:08:00 <bluelightning> I don't think we were going that far...
Jun 17 10:08:19 <bluelightning> having a BSP depend on meta-oe is a bit egregious though
Jun 17 10:11:13 <ant_work> RP: I'd trace a line saying the fs needed for building an image for MTD are apart
Jun 17 10:11:37 <ant_work> reiserfs, btrff.. are other stuff
Jun 17 10:12:10 <ant_work> former needed to build an image, latter for mounting it
Jun 17 11:37:18 <ant_work> RP: basically all the recipes providing a -native tool should belong to oe-core imho
Jun 17 11:38:15 <ant_work> but I understand your concerns about bloat
Jun 17 11:40:09 <Crofton|work> I think we should have one layer per recipe
Jun 17 11:44:20 <ant_work> this is the other risk ;)
Jun 17 11:45:23 <Crofton|work> :)
Jun 17 13:10:57 <heeen> can I tell oe where to create the shadow build dir
Jun 17 13:14:19 <bluelightning> heeen: sorry, could you explain further what you mean?
Jun 17 13:14:49 <heeen> BUILD-foo/work/arm-foobarbaz/package/work
Jun 17 13:15:08 <heeen> is there something like S_pn-package to change the location
Jun 17 13:16:10 <bluelightning> heeen: there is B if that's what you mean
Jun 17 13:16:34 <bluelightning> i.e. B_pn-recipename
Jun 17 17:07:57 <morphis> heeen: put something like S_pn-<packagename> = "<path to source>" into your conf/local.conf
**** ENDING LOGGING AT Tue Jun 18 02:59:59 2013