**** BEGIN LOGGING AT Thu Apr 18 02:59:58 2013
Apr 18 06:43:53 <bluelightning> morning all
Apr 18 06:45:45 <mihai> morning bluelightning
Apr 18 06:48:42 <mattnie> morning bluelightning
Apr 18 06:53:46 <bluelightning> hi mihai, mattnie
Apr 18 07:25:21 <mckoan> good morning
Apr 18 07:28:51 <mattnie> hi mckoan :)
Apr 18 07:35:17 <mcfrisk> Hi, is there a way to build yocto images from the rpm repo alone? Like with meego image builder..
Apr 18 07:39:50 <thaytan> denix: no, no mention of TARGET_ARCH anywhere
Apr 18 07:46:24 <thaytan> I took out rm-work and it doesn't rebuild it now
Apr 18 07:48:41 <bluelightning> thaytan: rm_work behaviour has improved quite a bit recently
Apr 18 07:52:55 <bluelightning> FWIW
Apr 18 08:54:01 <Sput> mcfrisk: hej :)
Apr 18 08:55:07 <mcfrisk> Sput: hi
Apr 18 08:55:29 <Sput> mcfrisk: I was wondering why you would ask the same question that I got this morning, and then figured out who you are :)
Apr 18 08:56:29 <Sput> in any case, one can just execute the do_rootfs task, which *should* work, but in the end fails with some buildhistory exception
Apr 18 09:00:36 <RP> mcfrisk: It has worked in the past and I know people are looking at it in the 1.5 cycle but right now its not supported directly
Apr 18 09:05:55 <mcfrisk> RP, Sput: thanks. I guess it could also be possible to debootstrap and similar rpm package tools to unpack packages from a yocto output repository.
Apr 18 09:06:12 <Sput> mcfrisk: or even use MIC directly, maybe?
Apr 18 09:06:36 <mcfrisk> yep, could be made to work
Apr 18 09:07:58 <mcfrisk> In maemo world images were heavily configured with virtual packages and long dependency chains, I liked the rpm package build and image creation separation in meego. Now yocto has quite deeply merged these two integration steps.
Apr 18 09:08:44 <RP> mcfrisk: They're not that tightly coupled, we generate the packages, the image creation code then builds images with them based on few inputs
Apr 18 09:09:10 <RP> mcfrisk: the only tricky part is we have extra data around in the form of pkgdata which we use to make some choices at image construction time
Apr 18 09:09:26 <RP> all the data is in the packages, its just hard to get at so we have an easier abstraction
Apr 18 09:09:42 <RP> (particularly since we have to deal with three package formats)
Apr 18 11:27:25 <hrww> re
Apr 18 12:03:55 <otavio> how long danny will be maintained?
Apr 18 12:06:22 <otavio> I didn't find this info in the wiki
Apr 18 12:25:11 <panda84kde> otavio: it's me the diego.ml@zoho of the mailing list, fyi. programming the fresh build right now
Apr 18 12:32:56 <otavio> panda84kde: oh; cool
Apr 18 12:33:03 <otavio> panda84kde: let me know how it goes for you
Apr 18 12:33:13 <panda84kde> otavio: just tested. Fail.
Apr 18 12:33:24 <otavio> panda84kde: I have some more patches for rolling out today but does not affect this
Apr 18 12:33:24 <panda84kde> [484343.712] (II) VIVANTE(0): test Initializing EXA
Apr 18 12:33:28 <panda84kde> and nothing more
Apr 18 12:33:28 <otavio> panda84kde: which machine?
Apr 18 12:33:36 <panda84kde> nitrogen6x
Apr 18 12:33:46 <panda84kde> rev1
Apr 18 12:33:50 <otavio> panda84kde: curious
Apr 18 12:33:56 <Crofton|work> zedii, got a minute for hopefully a stupid problem?
Apr 18 12:34:00 <otavio> panda84kde: and which image?
Apr 18 12:34:07 <panda84kde> fsl-image-gui
Apr 18 12:38:40 <otavio> panda84kde: and it does not show the dri init?
Apr 18 12:39:32 <panda84kde> same exact thing on a nitrogen6x rev2 board and an LVDS panel
Apr 18 12:40:11 <panda84kde> otavio: fulll log. http://pastebin.com/JjzDCpEH
Apr 18 12:40:24 <Crofton|work> how do the kenel tools work out KARCH?
Apr 18 12:40:30 <Crofton|work> that is the question!
Apr 18 12:41:19 <otavio> [4112707.854] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
Apr 18 12:41:19 <otavio> [4112707.969] (II) Module dri: vendor="X.Org Foundation"
Apr 18 12:41:27 <otavio> panda84kde: this should have failed
Apr 18 12:43:10 <panda84kde> ok, fixing manually to see if it works
Apr 18 12:43:12 <zedii> Crofton|work, pong
Apr 18 12:43:17 <Crofton|work> hey
Apr 18 12:43:22 <Crofton|work> I've got a stupid issue
Apr 18 12:43:32 <Crofton|work> using linux-yocto-custom
Apr 18 12:44:04 <Crofton|work> http://pastebin.com/ue6c9nKk
Apr 18 12:44:15 <Crofton|work> this is git repo + defconfig
Apr 18 12:44:56 <zedii> interesting. can you pastebin the meta-series ?
Apr 18 12:45:00 <Crofton|work> sure
Apr 18 12:45:09 <Crofton|work> it seems to be missing things :)
Apr 18 12:45:35 * zedii smells a bug :P
Apr 18 12:46:15 <Crofton|work> http://pastebin.com/Cxr1Ka1D
Apr 18 12:47:02 <Crofton|work> I have siilar stuff for the product that shall remain nameless that works :)
Apr 18 12:47:33 <Crofton|work> which seems odd to me
Apr 18 12:47:49 <zedii> hmm. yup. way empty. but yet this was tested not three days ago.
Apr 18 12:47:51 <panda84kde> otavio: you are right. Wrong link :) Correct paste here: http://pastebin.com/Pqh1wtEa
Apr 18 12:48:06 <Crofton|work> three days is an eternity
Apr 18 12:48:14 <Crofton|work> I am not saying my configs are "corect"
Apr 18 12:48:18 <panda84kde> libdri.so now fails, but result doesn't change
Apr 18 12:48:25 <zedii> Crofton|work,  to answer your question. KARCH comes from the top level board description, which should be generated for a custom board on your behalf.
Apr 18 12:48:27 <Crofton|work> but the weird thing is I swear this worked recently
Apr 18 12:48:34 <zedii> heh. I'm swearing.
Apr 18 12:48:45 <Crofton|work> generated by who?
Apr 18 12:48:57 * Crofton|work does not used automegical tools 
Apr 18 12:49:31 <zedii> the tools themselves, just a small entry point, to prevent the masses from needing it :)
Apr 18 12:49:38 <Crofton|work> ok
Apr 18 12:49:51 <zedii> Crofton|work, without handing away anything I can't see, what's the easiest way for me to try this here?
Apr 18 12:50:10 <Crofton|work> let me update soemthing on github
Apr 18 12:52:48 <Crofton|work> zedii, https://github.com/balister/meta-ettus/commits/e100-updates
Apr 18 12:53:11 <Crofton|work> bacially, I am trying to get some old stuff working again
Apr 18 12:53:21 <Crofton|work> I fear I missed some small but critical detail
Apr 18 12:53:22 <zedii> np. I'm cloning it now.
Apr 18 12:53:46 <Crofton|work> however, hopefully my failings help you harden the code :)
Apr 18 12:54:08 <zedii> heh. no doubt. I always say "thanks" to bug reports .. but it always feels wrong :P
Apr 18 12:55:31 <ant_work> Crofton|work: heh, poor Bruce is pestered by us abusing of kernel-tools in unproper ways...
Apr 18 12:55:54 * zedii is just pestered by his crappy assumptions as he removes years of cruft :P
Apr 18 12:58:04 <Crofton|work> I am tryin gto work in such a way that in ten years when lnux-tocto uses a linux version that supports vendor hardware without a million patches, the kconf frags just work
Apr 18 12:58:54 <zedii> Crofton|work, so it's the e100-updates branch ?
Apr 18 12:58:55 <ant_work> oh, I'm almost there with devices now out-of-production
Apr 18 12:59:00 <Crofton|work> yes
Apr 18 12:59:11 <Crofton|work> ant_work, rofl
Apr 18 12:59:24 <Crofton|work> ant_work, btw how easy is it to buy sim cards in Italy
Apr 18 12:59:27 <ant_work> ..but regulatly broken by upstream changes untested on old hw
Apr 18 13:00:33 <panda84kde> Crofton|work: really easy
Apr 18 13:00:43 <panda84kde> you can have one for free generally :)
Apr 18 13:01:13 <ant_work> Crofton|work: hm.. rechargeable is easy but I don't know if foreigers need to show id-card like we do
Apr 18 13:01:33 <ant_work> it's all registered....
Apr 18 13:02:18 <Crofton|work> I saw something on needing an id card
Apr 18 13:07:10 <silviof> I have some problems to compile qt4. I have paste it here: http://pastie.org/private/oft6ttf8whvz0a13qmwcq -- have someone a solution for this? Saerching with google brings me only to gcc-bugs from 2007.
Apr 18 13:09:12 <zedii> Crofton|work, I launched a build .. it's fetching. I'll let you know when I find the problem.
Apr 18 13:11:13 <Crofton|work> thanks
Apr 18 13:11:20 <Crofton|work> I have to run an errnad for my wife
Apr 18 14:00:41 <mattnie> I started with developing own applikations and read the dev-manual, I want to add a simple helloworld.c to my image, but now I have 2 questions. It requires a recipe that has the file listed in the SRC_URI variable. Do I have to ad e. g. in meta-yocto-bsp/recipes-core/packagegroup-core-base.bbappend and insert SRC_URI to it?
Apr 18 14:02:59 <mattnie> I did not get familiar with the documentation in my opionen there are missing some steps for beginners
Apr 18 14:05:45 <mattnie> I am at 5.3.1 @ http://www.yoctoproject.org/docs/1.4/dev-manual/dev-manual.html#usingpoky-extend-addpkg-singlec
Apr 18 14:34:59 <zeddii> Crofton|work, good news. and bad news. your board configures and works perfectly for me. Can you pastebin me your layer hashes ?
Apr 18 14:35:34 <panda84kde> otavio: are you working on the issue by being able to reproduce the problem on the Nitrogen6x board, or are just working on it?
Apr 18 14:35:56 <otavio> panda84kde: I am finishing a new build to start checking it
Apr 18 14:36:31 <panda84kde> perfect. if you want me i'm here.
Apr 18 15:51:33 <panda84kde> otavio: I'm leaving but I'll take a look at the mailing list.
Apr 18 16:41:29 <Crofton|work> zeddii, bother
Apr 18 16:41:43 <Crofton|work> let me try dropping layers first
Apr 18 16:41:49 <Crofton|work> maybe there is some weird conflict
Apr 18 16:43:34 <zeddii> FWIW: here's my configure log: http://pastebin.com/WiYEbrTc, I'm not up to date as of a few hours ago, I'll pull again and retry as well.
Apr 18 16:44:59 <Crofton|work> I removed all layers but oecore and ran cleansstate build
Apr 18 16:45:13 <Crofton|work> and it had the issue, so starting from completely clean now
Apr 18 16:45:24 <Crofton|work> meta              = "master:2453504004cfb6c9b5030b557f421e580802a280"
Apr 18 16:45:24 <Crofton|work> e100-bsp          = "e100-updates:a380993e2a4dfa89b8e49313ff5cb6e5baa6e778"
Apr 18 16:45:39 <Crofton|work> it iwll be a while, but I have a call in a few minutes
Apr 18 16:45:43 <Crofton|work> need to get sip on again
Apr 18 16:45:53 * zeddii nods
Apr 18 16:49:08 <Crofton|work> blew up again
Apr 18 16:49:09 <Crofton|work> wtf
Apr 18 16:49:22 <Crofton|work> on those revs
Apr 18 16:49:34 <Crofton|work> maybe I should go backwards on oe-core
Apr 18 16:49:41 * Crofton|work curses sip
Apr 18 16:54:59 <zeddii> hmm
Apr 18 16:55:36 <zeddii> there was a bug in linux-yocto custom, but it was fixed. hmm.
Apr 18 17:27:08 <Crofton|work> zeddii, I ran some build on random checkouts and still fails
Apr 18 17:27:14 <Crofton|work> weird wierd wierd
Apr 18 17:29:46 <zeddii> argh. I need a way to see it.
Apr 18 17:30:09 <zeddii> Crofton|work, here's the meta-series that was produced for my build: http://pastebin.com/Mv561vjm
Apr 18 17:30:16 <zeddii> you can see that I have the important missing parts.
Apr 18 17:30:48 <Crofton|work> this is on F17
Apr 18 17:31:01 <Crofton|work> how are they generated?
Apr 18 17:31:04 <zeddii> random ubuntu here.
Apr 18 17:31:13 <zeddii> hmm. could definitely be a host thing then.
Apr 18 17:31:20 <zeddii> I need to dig up a F17 box.
Apr 18 17:31:21 <Crofton|work> that is what worries me
Apr 18 17:31:40 <zeddii> give me a few minutes. I'll see what I can find.
Apr 18 17:32:04 * Crofton|work grasps at straws
Apr 18 17:37:27 <zeddii> Crofton|work, I have a machine to use here. will let you know once I'm setup.
Apr 18 17:37:34 <Crofton|work> thanks
Apr 18 17:38:09 <Crofton|work> after i get off this call, I'll either dig further, or do a test build of gnuradio next :)
Apr 18 17:38:26 <zeddii> go for the latter, until I come back with wild claims it works :P
Apr 18 17:38:48 <Crofton|work> thanks
Apr 18 17:38:50 <Crofton|work> I owe
Apr 18 17:38:52 <Crofton|work> you
Apr 18 17:38:55 <zeddii> Crofton|work, 32 or 64 bit ? I have a choice here, might as well make it exaclty the same.
Apr 18 17:39:01 <Crofton|work> 64
Apr 18 17:39:10 <zeddii> cool.
Apr 18 17:39:31 <Crofton|work> there is a gnuradio release coming up and I haven't run it through the recipe lately to look for pain inflicted
Apr 18 17:39:37 <Crofton|work> by devs :)
Apr 18 17:39:55 <zeddii> never! pain by devs ?
Apr 18 18:10:06 <alex_kag> hello. does bitbake can download git repository on ssh Protocol?
Apr 18 18:14:58 <khem> can bitbake handle '@' in directory name ?
Apr 18 18:15:06 <khem> i am seeing interesting problem
Apr 18 18:32:47 <zeddii> Crofton|work, F17 worked here. W.T.F.
Apr 18 18:32:51 <zeddii> http://pastebin.com/8hxyw4bv
Apr 18 18:33:25 <Crofton|work> I build only against oe-core
Apr 18 18:33:27 <Crofton|work> ?
Apr 18 18:35:43 <zeddii> I'll clone that then!
Apr 18 18:36:31 <Crofton|work> that should work
Apr 18 18:36:43 <Crofton|work> I suspect I am one of the few people doing minimal builds
Apr 18 18:37:18 <zeddii> no worries. easy for me to clone and rebuild on this VM.
Apr 18 18:38:52 <Crofton|work> heh
Apr 18 18:38:57 <Crofton|work> I figured you had something like that
Apr 18 18:39:05 <Crofton|work> I ahve the gnuradio build going
Apr 18 18:39:30 <Crofton|work> I need to clean off the old machines and update them for this purpose
Apr 18 18:43:16 <Crofton|work> zeddii, you can't think of anything stupid I could do to make this happen?
Apr 18 18:45:35 <zeddii> nope. everything you have is fine.
Apr 18 18:46:03 <zeddii> so I want to hunt this down, since the dumb probably lies between my keyboard and chair :P
Apr 18 18:46:22 * zeddii clones bitbake
Apr 18 18:47:22 <Crofton|work> hmm
Apr 18 18:47:46 <Crofton|work> is what I have
Apr 18 18:47:50 <Crofton|work> 414fe98fe367ba44ea0fd20d8fe1296bcef58ea6
Apr 18 18:52:01 <Crofton|work> at the very least a better message would help :)
Apr 18 18:56:09 <zeddii> 414fe98fe367ba44ea0fd20d8fe1296bcef58ea6 ?
Apr 18 19:24:14 <Crofton|work> zeddii, bitbake version
Apr 18 19:27:44 <zeddii> aha. ok. let me confirm that here. I'm still waiting for the kernel to fetch. not sure why it's taking so long.
Apr 18 19:33:16 <kergoth> Crofton|work, zeddii: what issue are you hitting ,out of curiosity?
Apr 18 19:36:48 <Crofton|work> issue building with linux-yocto-custom
Apr 18 19:36:55 <Crofton|work> or do you need more details?
Apr 18 19:37:06 <kergoth> ah
Apr 18 19:37:17 <kergoth> no, was just curious, and i've never used that, so not going to be of much help :)
Apr 18 19:37:22 <zeddii> Crofton|work, *still* works for me.
Apr 18 19:37:25 <zeddii> http://pastebin.com/HfJQD9ee
Apr 18 19:37:29 <zeddii> @#$
Apr 18 19:37:53 <Crofton|work> bother
Apr 18 19:38:05 <Crofton|work> I won't be able to look hard until Monday
Apr 18 19:38:12 <zeddii> seriously. I just want to see it break, so I can poke at the wreckage.
Apr 18 19:38:17 <Crofton|work> I need to not work tomorrow
Apr 18 19:38:23 <zeddii> I'll keep looking at it, I don't want to be in your way.
Apr 18 19:38:31 <zeddii> heh. I planned on not working tomorrow too :P
Apr 18 19:38:34 <Crofton|work> BB_VERSION        = "1.17.1"
Apr 18 19:38:49 <Crofton|work> hmm
Apr 18 19:39:14 <zeddii> there shouldn't be any hooks between the two, I just reset mine to the commit you mentioned.
Apr 18 19:39:29 <zeddii> and started another.
Apr 18 19:40:43 <zeddii> still works! http://pastebin.com/0dbJZ6Xv
Apr 18 19:51:15 <Crofton|work> in the good news department, I downloaed my dive computer into subsruface
Apr 18 20:32:53 * mranostay waves
Apr 18 21:13:06 <darknighte> anyone tried to use a PREMIRROR for a file:// SRC_URI before?
Apr 18 22:04:31 <mranostay> howdy darknighte
Apr 18 22:05:01 <darknighte> how's it going mranostay?!  been a bit...
Apr 18 22:05:14 <darknighte> you at collab?
Apr 18 22:06:59 <mranostay> snuck in on Tuesday and Wedneday
Apr 18 22:07:06 <mranostay> *Wednesday
Apr 18 22:08:31 <mranostay> ka6sox: well back to land of the living^H^H^HHnerds
Apr 18 23:40:26 <kergoth> Gah, this gettext madness is biting me hard
Apr 18 23:40:56 <kergoth> when you have GPLv3 in INCOMPATIBLE_LICENSE, you end up with new (0.18) gettext-minimal-native and gettext-native, but old (0.16) target gettext
Apr 18 23:41:08 <kergoth> but of course the aclocal paths for both native and target end up in the aclocal search path
Apr 18 23:41:31 <kergoth> so it's possible for it to pick up the 0.16 macros and try to use that with projects whose po/Makefile.in.in came from 0.17 or 0.18
Apr 18 23:42:04 <kergoth> and thats assuming that 0.18's tools are compatible with 0.16 on the target
Apr 18 23:42:21 <kergoth> and i have no clue when it is and when it isn't safe to run autopoint vs gettextize, and when to use one vs the other
Apr 18 23:42:32 <kergoth> Anyone know more about gettext around that can advise?
Apr 18 23:42:57 * kergoth thinks there isn't a great deal of testing happening with INCOMPATIBLE_LICENSE usage
Apr 18 23:59:42 <bluelightning> kergoth: I think we explicitly say you're not meant to change INCOMPATIBLE_LICENSE with the same tmpdir
Apr 18 23:59:56 <bluelightning> in the manual, that is
Apr 19 02:24:49 <kergoth> hah. I don't know how I missed it, but the python standard library already provides a module for determining a python script's imports -- http://docs.python.org/2/library/modulefinder. could use that to implement automatic python rdeps even more trivially
**** ENDING LOGGING AT Fri Apr 19 02:59:58 2013