**** BEGIN LOGGING AT Fri Mar 26 02:59:57 2010 **** BEGIN LOGGING AT Fri Mar 26 13:06:14 2010 **** ENDING LOGGING AT Fri Mar 26 13:09:37 2010 **** BEGIN LOGGING AT Fri Mar 26 13:12:14 2010 Mar 26 19:47:44 hello, can anybody help me with http://effik.pastebin.com/iYRpp8Fi ? Mar 26 23:52:37 anyone around? Mar 26 23:53:42 I have a question: is the git org.openembedded.stable branch still relevant or is this outdated badly? Mar 26 23:58:53 !logs Mar 27 02:20:40 Anybody on here? Mar 27 02:20:55 check the date on the last commit on that branch? :P Mar 27 02:21:06 Hi Mar 27 02:21:18 hi! :P Mar 27 02:21:24 I think its like 16 months Mar 27 02:21:39 In that case, I might be inclined to say that it's outdated :P Mar 27 02:22:13 dev is probably newer, but I was looking for something more ... stable Mar 27 02:22:38 ahh Mar 27 02:22:47 I remember reading somewhere that the devs were going to do a stable branch Mar 27 02:22:49 wish i could help. I'm dealing with a random insane problem of my own :P Mar 27 02:23:59 Something about companies wanting something with a 5 or 10 year support horizon, I thought that was stable... But I guess there wasn't enough interest Mar 27 02:24:17 what problems are you having? Mar 27 02:25:43 gettext-native (0.17) is linking the system's libxml (by path) instead of the prebuild libxml2-native :( Mar 27 02:26:07 and failing because the staged libz doesn't have gzopen64, which my system's libxml2 requires Mar 27 02:26:52 popping into a devshell right now to see if there's anything I can do about it :( Mar 27 02:27:12 that is a problem Mar 27 02:28:04 I also don't really understand why we need to build most of an entire native sysroot… it seems like it would cut off an entire 50% of the rules to use the host system's tools instead of reinventing them Mar 27 02:28:13 i've never had that problem with bitbake Mar 27 02:28:16 hrm :( Mar 27 02:31:23 Do you mean the toolchain? Obviously gcc needs to be specific to target hardware, but I guess all of perl, m4, etc... could be same Mar 27 02:38:03 Right. Everything but the cross-compiler. Mar 27 02:38:32 I've got the latest perl, m4, etc. (to paraphrase) installed, so it doesn't seem like much of a stretch to just use them instead Mar 27 02:39:13 I agree Mar 27 02:39:32 Kindof silly rebuilding everything just so you can build NANO Mar 27 02:39:48 exactly Mar 27 02:39:58 what device are you using angstrom on? Mar 27 02:40:31 a gumstix Overo Mar 27 02:40:45 thats a neat little device Mar 27 02:40:47 Howsabout you? Mar 27 02:40:50 very :D Mar 27 02:41:01 still messing around with zaurus.. I have an akita and collie Mar 27 02:41:14 ooh, nice Mar 27 02:41:17 I always wanted a Zaurus Mar 27 02:41:37 they are awesome, but software was always what I felt really left the whole package behind Mar 27 02:41:44 Very far ahead of their time Mar 27 02:41:52 aye Mar 27 02:42:24 ouch, gettext is trying to link more than my native libxml Mar 27 02:42:30 /usr/lib64/libacl.so /usr/lib64/libattr.so /usr/lib64/libcroco-0.6.so /usr/lib64/libglib-2.0.so /usr/lib64/libxml2.so Mar 27 02:42:44 I found it pretty frustrating with OE and OZ and all that... every time it would get close to being usable, something would break. Usually a new kernel would break stuff Mar 27 02:42:50 hehe Mar 27 02:42:54 sounds like my desktop linux system :-/ Mar 27 02:43:18 No sense having the newest kernel when your SD/MMC just stopped working Mar 27 02:44:05 Its not like the zaurus hardware has changed so much that it needs a new kernel every half year. Hardware hasn't changed for 6 years. Mar 27 02:44:24 right Mar 27 02:44:47 so why would gettext want to link against your native libxml? Mar 27 02:45:06 can't find the one built by toolchain? Mar 27 02:45:10 good question.. i picked through the recipe and can't find anything about it Mar 27 02:45:18 it almost seems like autoconf is causing it Mar 27 02:45:44 which is funny because there's a patch disabling some library searching which pretty much says says "let autoconf handle it, it's smarter than we are" Mar 27 02:47:06 is the one you want actually built? Mar 27 02:47:28 I'm pretty sure Mar 27 02:47:38 I haven't done any modifications to this tree yet, so i'm going with the current defaults Mar 27 02:47:58 might want to check the .so file is actually around Mar 27 02:48:26 Could be autoconf is being smart because it can't find one you want? Mar 27 02:49:00 hmm.. Mar 27 02:49:02 definitely there Mar 27 02:49:02 ./staging/x86_64-linux/usr/lib/libxml2.so Mar 27 02:49:45 Should it be using the one for arm architecture? Mar 27 02:50:12 nah, it's building gettext-native Mar 27 02:50:33 oh, for x86_64 as part of toolchain, not for a ipkg Mar 27 02:50:36 I wonder if I could be sneaky and link my system libz over the staged native libz, thus resolving the "missing symbols" ;) Mar 27 02:56:32 a-ha Mar 27 02:56:46 About gettext-0.17: "so if no headers are found, it assumes no external support, but it doesnt bother clearing out the discovered library values …" Mar 27 02:56:55 and something about the libxml2 headers I have staged is broken Mar 27 02:57:00 (which i saw in the config log) Mar 27 02:57:46 needs headers? Mar 27 02:57:48 and it will be fixed in gettext 0.18? … i've been banging my head against a KNOWN BUG for a WEEK?! Mar 27 02:58:19 It's an include dir problem. usr/include/libxml2 isn't -I, but it's looking for libxml/blah.h (instead of libxml2/libxml/blah.h) Mar 27 02:58:40 the configure script is "failing" to find the headers for the staged libxml because the test program fails Mar 27 02:59:00 hmmm **** ENDING LOGGING AT Sat Mar 27 02:59:56 2010