**** BEGIN LOGGING AT Sun Oct 12 02:59:57 2008
**** ENDING LOGGING AT Sun Oct 12 03:14:00 2008

**** BEGIN LOGGING AT Sun Oct 12 03:14:13 2008
Oct 12 12:15:43 <drasar> Hello everybody. I have downloaded an Angstrom build for HTC Blueangel and I have find out that "file" utility says this on binaries: "ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.14, stripped". Does it mean that these binaries are runnable only on kernel >=2.6.14? If so, how can I compile source to be runnable on older kernels as well?
Oct 12 12:27:27 <johnx> you can download the openembedded build system from http://wiki.openembedded.net/index.php/Getting_Started
Oct 12 12:27:41 <johnx> Does the blueangel really not have a more recent kernel available?
Oct 12 12:41:21 <drasar> johnx: Yes, I know how to do my own build, but I need to be it runnable on 2.6.12 kernel, because I would like to use it on HTC Himalaya ;)
Oct 12 12:41:44 <johnx> so you need to build oabi binaries for one thing
Oct 12 12:42:21 <johnx> I'm honestly a little fuzzy on what file means about the "for 2.6.8" or whatever
Oct 12 12:45:50 <drasar> johnx: I have tried to run /sbin/init with "for GNU/Linux 2.6.14" on 2.6.12 and it freeezes.
Oct 12 12:47:08 <johnx> well, prior to 2.6.16 (or so) the kernel didn't have support for eabi binaries, and if the blueangel is a armv5 or better it probably has EABI binaries built for it
Oct 12 12:55:37 <drasar> johnx: How can I recognize that the binaries has EABI?
Oct 12 13:04:13 <johnx> what feed does it pull from? armv5te should be eabi and armv4 should be oabi, I believe
Oct 12 13:04:23 <johnx> I think there was a way to be more sure, let me check
Oct 12 13:08:44 <ESI> hi there, I got a question about how the kernel versions are chosen. I have dev and stable path compiled for akita, dev uses 2.6.23, and stable 2.6.24 which is a little weird. Is the best way to use preferred version in local.conf?
Oct 12 13:09:34 <johnx> if you want something different than the default, specifying it in local.conf seems reasonable
Oct 12 13:10:29 <johnx> I think that whoever tests the zaurus cxx00 kernel must test mainly on spitz, because it appears that the linux-rp*.bb files have different preferences for akita vs spitz
Oct 12 13:10:38 <johnx> that being said I'm using 2.6.26 happily
Oct 12 13:10:43 <johnx> (on an akita)
Oct 12 13:16:08 <ESI> johnx: where do I find the linux-rp*.bb-files?
Oct 12 13:16:43 <johnx> in org.openembeded.dev/packages/linux/
Oct 12 13:16:57 <johnx> replace 'dev' with stable or whatever you're using of course
Oct 12 13:23:31 <ESI> johnx: I am using dev and stable in parallel directories. I looked at the files, but I do not see how the default is decided...
Oct 12 13:27:27 <johnx> not completely sure
Oct 12 13:27:37 <drasar> johnx: So what I should set in default.conf? ANGSTROM_MODE = "glibc"?
Oct 12 13:28:52 <johnx> ESI, I would set it in local.conf like you said or build it manually (bitbake linux-rp-2.6.26)
Oct 12 13:28:54 <johnx> drasar, hmm
Oct 12 13:29:07 <johnx> drasar, setting glibc won't make a difference
Oct 12 13:29:25 <johnx> is there a reason you need to run the same binaries on both machines?
Oct 12 13:32:44 <drasar> johnx: It will be fine to have the same binaries, but will be bearable to have two builds
Oct 12 13:33:44 <ESI> johnx, thank you for your hints, I am now trying building manually. When I build 2.6.24 manually, will it be automatically chosen next time I build an image?
Oct 12 13:34:13 <johnx> ESI, I'm pretty sure, yes
Oct 12 13:35:03 <ESI> thank you, that explains the differneces between my stable and dev path.
Oct 12 13:39:25 <johnx> drasar, I took a quick look at org.openembedded.dev/conf/distro/include/angstrom-glibc.inc
Oct 12 13:40:09 <johnx> drasar, looks like there's a simple check to see if an image is being built for a machine without eabi support and then eabi is disabled
Oct 12 13:40:21 <johnx> drasar, the line begins TARGET_OS = 
Oct 12 13:41:34 <johnx> also, might want to look at the FAQ: http://wiki.openembedded.net/index.php/Category_talk:FAQ#8._What_is_ARM_EABI_and_how_do_I_use_it.3F
Oct 12 14:25:52 <drasar> johnx: Thanks for the link. There is said that I should use "TARGET_OS=-gnueabi" for EABI but what I should set when I need OABI?
Oct 12 14:27:57 <drasar> And what is "org.openembedded.dev/conf/distro/include/angstromoabi.inc" for?
Oct 12 14:33:47 <johnx> drasar, at this point all I could do is guess :/
Oct 12 14:35:22 <johnx> drasar, are you 100% sure there's no kernel later than 2.6.12 for the himalaya?
Oct 12 14:42:06 <drasar> johnx: It is possible to use 2.6.21-hh20 on Himalaya (it boots), but a lot of drivers are not ported from 2.6.12-hh2-xda0-ba0 kernel :(
Oct 12 14:44:46 <johnx> drasar, maybe tweak the distro conf for angstrom to just say: 
Oct 12 14:44:50 <johnx> TARGET_OS = linux
Oct 12 14:45:18 <johnx> ARM_ABI = oabi
Oct 12 14:46:18 <drasar> johnx: Ok, I will try it. Thanks a lot ;)
Oct 12 14:46:37 <johnx> that is seriously a complete guess
Oct 12 14:47:19 <johnx> if you do it in local.conf I think it will be overridden, so you might need to set it in org.openembedded.dev/conf/distro/angstrom-2008.1.conf
Oct 12 20:07:08 <mimecar__> hi
Oct 12 20:34:48 <mistergibson>  hello
Oct 13 01:21:56 <mistergibson> Does anyone: a) have any, or b) want to share any     insights into h5000 wifi issues?
**** ENDING LOGGING AT Mon Oct 13 02:59:57 2008