**** BEGIN LOGGING AT Thu Feb 08 02:59:59 2007
Feb 08 08:58:11 <Cockroach-> good day
Feb 08 08:58:15 <hrw> good
Feb 08 09:29:28 <_law_> who builds the angstrom unstable images?
Feb 08 09:29:39 <XorA> koen|away: 
Feb 08 09:35:37 <_law_> koen|away, could you also build images unstable images fpr gpe? or is this too much?
Feb 08 10:29:37 <_law_> btw. http://law.hostsen.net/oe/aximx50_oe_stuff_20070208.tar.bz2 aximx50 stuff is on the way :-)
Feb 08 12:14:21 <XorA> bleh
Feb 08 13:20:17 <goxboxlive> hrw are you there
Feb 08 13:24:01 <hrw> brb
Feb 08 13:28:55 <hrw> goxboxlive: go
Feb 08 13:34:56 <goxboxlive> good
Feb 08 13:35:07 <goxboxlive> hrw: You are a mebmer of the qtopia team right?
Feb 08 13:36:18 <hrw> opie2?
Feb 08 13:36:21 <goxboxlive> yes
Feb 08 13:37:18 <goxboxlive> Will we see it in OpenEmbedded soon? Or arent you goingt to add it?
Feb 08 13:39:37 <hrw> do not know
Feb 08 13:39:47 <hrw> I do not have time to work on it
Feb 08 13:45:27 <mccarthy> anyone know who built the h5000 images from yesturday?
Feb 08 13:45:41 <goxboxlive> ok
Feb 08 13:46:02 <XorA> mccarthy: 99% likely it was koen
Feb 08 13:46:14 <mccarthy> XorA, ok thanks
Feb 08 13:46:24 <mccarthy> for some reason all of my builds refuse to boot ....
Feb 08 13:46:42 <XorA> mccarthy: note koens tree doesnt always represent OE tree
Feb 08 13:46:42 <mccarthy> but there are issues with the testing builds (like modules that do not actually get packaged)
Feb 08 13:47:15 <mccarthy> XorA, hmm, that could explain it
Feb 08 13:47:34 <mccarthy> I think I will ask about the missing modules in #OE
Feb 08 15:46:34 <mccarthy> I give up on building angstrom images!
Feb 08 15:47:03 <mccarthy> they simply *refuse* to get past the "Freeing init memory" portion of booting
Feb 08 15:47:20 <hrw> kernel with EABI enabled?
Feb 08 15:47:21 <mickeyl> sounds like eabi/oabi issues
Feb 08 15:47:41 <mccarthy> hmm
Feb 08 15:47:55 <mccarthy> which should it be for a h5000 with a 2.6 kernel?
Feb 08 15:48:15 <mickeyl> that's not depending on kernel
Feb 08 15:48:19 <mickeyl> but on what toolchain you use
Feb 08 15:48:22 <mccarthy> oh
Feb 08 15:48:30 <mickeyl> if you build an eabi toolchain
Feb 08 15:48:33 <mickeyl> you need an eabi kernel
Feb 08 15:48:35 <mickeyl> and vice versa
Feb 08 15:48:40 <mickeyl> (oabi)
Feb 08 15:48:58 <mccarthy> koen|away, once told me to do oabi for h5000 if using a 2.4 kernel
Feb 08 15:49:07 <mickeyl> yes, there is no such thing as eabi for 2.4
Feb 08 15:49:25 <mccarthy> hmm
Feb 08 15:49:39 <hrw> eabi req 2.6.16 kernel or newer
Feb 08 15:49:58 <mccarthy> I simply built with MACHINE=h5000 and DISTRO=angstrom-2007.1
Feb 08 15:50:06 <mickeyl> probably too simple
Feb 08 15:50:09 <mickeyl> check defconfig for h5000
Feb 08 15:50:12 <mickeyl> or recipe
Feb 08 15:50:12 <mccarthy> should I have specified eabi somewhere?
Feb 08 15:50:18 <mickeyl> whether  there is eabi enabling magic
Feb 08 15:50:22 <mickeyl> can be either in recipe or in defconfig
Feb 08 15:50:30 <mccarthy> there is a defconfig for h5000 that was used
Feb 08 15:50:30 <mickeyl> see linux-rp for example
Feb 08 15:50:35 <mickeyl> we do it in recipe
Feb 08 15:50:40 <mickeyl> which is more flexible
Feb 08 15:52:38 <mccarthy> the defconfig says CONFIG_AEABI=y
Feb 08 15:52:53 <mccarthy> and also CONFIG_OABI_COMPAT=y
Feb 08 15:53:15 <hrw> so it is eabi ready
Feb 08 15:53:40 <mccarthy> does that mean that it is some other problem or that I needed some other magic somewhere else?
Feb 08 15:54:59 <mccarthy> doh
Feb 08 15:55:10 <mccarthy> I looked in the defconfig and saw the EABI thing
Feb 08 15:55:34 <mccarthy> but when I actually look in tmp/work/ at the .config in the kernel build dir, so such flag set!
Feb 08 15:57:44 <mccarthy> so where else should I be putting that? mickey|away said "recipe" which I presume means the .bb file, but which? (linux-handhelds-2.6_2.6.16-hh9.bb?) and how?
**** ENDING LOGGING AT Fri Feb 09 03:00:00 2007