**** BEGIN LOGGING AT Mon Jul 16 02:59:58 2007 Jul 16 11:33:56 psokolovsky: you there? Jul 16 11:43:14 how do i tell bitbake to ignore a binary which was compiled for another archecture? all i want to do is keep some windows binaries on my device but i want to automate it all using a bitbake recipe Jul 16 11:43:30 it keeps failing when doing the package QA task which bitbake inserts Jul 16 11:43:42 i have no control over this task, or do i? Jul 16 11:44:06 MrEMaN: You should be able to override the event surrounding do_package which invokes the QA; I'm not sure on the specifics though Jul 16 11:46:04 NAbyss: the event which does the QA is inserted by bitbake so i dont think i can change it Jul 16 11:46:32 NAbyss: is there anyway i can tell bitbake to just leave it alone? Jul 16 11:47:19 MrEMaN: Take a look at insane.bbclass; IIRC, that's the file that does the QA injection Jul 16 11:48:00 ah, do_package_qa Jul 16 11:48:47 yeah do_package_qa! :( Jul 16 11:48:58 MrEMaN: the question you want to answer to yourself and audience is *why* you want to keep some windows binaries on your device, and even with bitbake's help Jul 16 11:49:55 psokolovsky: because im using the recipe to install dependencies for an application and i wish to also store some windows binaries Jul 16 11:50:11 so i thoguth i would write a recipe instead of having a recipe for dependencies Jul 16 11:50:22 and then a script to retrieve the windows binaries Jul 16 11:50:37 anything terrible about that? Jul 16 11:50:46 i just dont see what the problem is Jul 16 11:50:53 MrEMaN: If you override the do_*_qa, I'd imagine that'd stop the behaviour Jul 16 11:51:13 NAbyss: i dont think you can, i will give it a go tho Jul 16 11:52:00 yep, me too ;-I sorry, without good reason to do something, I guess there's no need to go by run and length to just do it. YMMV Jul 16 11:55:09 ..? since when do i need to give a reason to write my own recipe? it may be different than standard stuff you may wish to do with bitbake but so what.. Jul 16 11:56:27 NAbyss: lol, i cant believe it worked Jul 16 11:56:47 i thought i read that you couldn't override those tasks Jul 16 11:56:54 thx Jul 16 11:56:57 np Jul 16 12:31:43 hi here Jul 16 12:33:30 first irc chat with angstrom :-) Jul 16 12:36:18 !seen xtor Jul 16 12:36:20 vanguard, I don't remember seeing xtor. Jul 16 12:36:36 !seen xoar Jul 16 12:36:37 vanguard, I don't remember seeing xoar. Jul 16 12:41:57 !see xort Jul 16 12:42:16 !seen xort Jul 16 12:42:17 summatusmentis, I don't remember seeing xort. Jul 16 12:42:52 vanguard: you're looking for the person yesterday who had a name very similar to XorA|gone right? Jul 16 12:43:10 yes, I did. Jul 16 12:44:09 I sent him my images (lasted about 6 hours), and wanted to know, if they were helpfully for him. Jul 16 12:44:22 I can't remember what his nick was Jul 16 12:44:39 He will recognize me, I think. Jul 16 13:28:36 !seen xota Jul 16 13:28:38 xota (n=xota@87.Red-81-36-172.dynamicIP.rima-tde.net) was last seen quitting from #gpe-project 10 hours, 54 minutes ago stating ({"Abandonando"}). Jul 16 13:29:02 that's what it was Jul 16 13:29:09 ~praise Laibsch Jul 16 13:29:19 !praise Laibsch Jul 16 13:29:20 * cdbot2 bows down to Laibsch and chants, "I'M NOT WORTHY!!" Jul 16 15:04:26 I'm getting an error when trying to build angstrom in glibc-intermediate (Gentoo amd64 host system) with the error of "configure: error: Need linker with .init_array/.fini_array support." Anyone seen this before? Jul 16 15:05:04 I'm building using the master makefile. Jul 16 15:08:21 hi Jul 16 15:10:16 howdy Jul 16 15:15:47 Interesting, works fine on my old Gentoo x86 system... Jul 16 15:48:43 Dang, I spoke too soon. Failed in the same way. Jul 16 17:04:05 re Jul 16 17:05:03 xota: Did you try my images? Jul 16 18:04:14 hi Jul 16 18:09:46 howdy Jul 16 18:10:02 hi joshin Jul 16 19:17:03 what is the package for the expose theme? Jul 16 19:44:23 is anyone around? Jul 16 20:05:46 hello all Jul 16 20:29:45 hi reyawn Jul 16 20:30:26 hello mimecar Jul 16 20:30:48 I finally got a usb net connection working on my angstrom build for IPAQ 5450, which was nice Jul 16 20:31:01 still no wireless, but it is an exciting advancement nonetheless Jul 16 20:31:10 yes, it is Jul 16 20:32:20 what devices does everyone here use? Jul 16 20:32:27 mime? :) Jul 16 20:33:11 i have a collie (zaurus sl550) and an akita (zaurus c1000) Jul 16 20:33:18 sl5500 Jul 16 20:33:50 nice, I need to pick up a different platform one of these days Jul 16 20:33:59 About to try Angstrom on a Collie/SL5500 and a Nokia770... Jul 16 20:34:03 akita is a great device Jul 16 20:34:08 initially I got into it from reading handhelds org, which is a bit more oriented towards IPAQ Jul 16 20:34:36 but inactivity there and other drama pointed me towards angstrom, which seems to be more devoted to the zaurus devices and such Jul 16 20:34:49 joshin: there's n image with gpe for collie, i don't know if it works ok Jul 16 20:35:08 reyawn: angstrom is a mixture of openzaurus, familiar... Jul 16 20:35:56 mimecar: I'm building my own image. My collie is just a test platform for Angstrom before I put it on the 770. (My collie's screen is slowly dying) Jul 16 20:36:11 ahh Jul 16 20:36:49 mimecar: ah...well, it does seem to work remarkedly well, even if things like the battery aren't supported yet Jul 16 20:38:20 i have installed angstrom only on my zaurus c1000 Jul 16 20:40:16 hi jos2 Jul 16 20:40:35 reyawn: angstrom use a 2.6 kernel, it's a big change for collie Jul 16 20:40:36 hi mimecar Jul 16 20:42:09 mimecar: true, it is a big change Jul 16 20:42:27 i have a nokia n770 and i wish to install angstrom into to it Jul 16 20:42:39 I'm not that familiar with these devices myself, but I bought the IPAQ 3 weeks ago solely for the purpose of experimentation with linux Jul 16 20:42:49 it seems fairly capable so far Jul 16 20:43:24 any kowns who to istalll it Jul 16 20:43:45 jos2: is there a release for 770 ? Jul 16 20:44:47 yes mimrcar Jul 16 20:44:58 a moment plis Jul 16 20:45:03 please Jul 16 20:46:03 reyawn: you can install familiar on the ipaq Jul 16 20:46:24 yes Jul 16 20:46:58 mimecar: yes, I did that...but the 2.4 kernel, and although it supports everything my curiosity wants me to run something newer and in more rapid development Jul 16 20:47:24 then, play with angstrom Jul 16 20:47:34 yes, I am working with it now Jul 16 20:47:39 buid the open embedded build system and compile programs Jul 16 20:47:43 I id Jul 16 20:47:45 *did Jul 16 20:47:55 running a build as of the 13th I believe Jul 16 20:48:03 did you followed tutorial from OE web? Jul 16 20:48:12 just gotta figure out wireless and battery Jul 16 20:48:32 well, I kinda followed a mesh of that and the "building angstrom" tutorial as well Jul 16 20:49:04 do you must set the stuff folder on the root or you can work in another folder ? Jul 16 20:49:29 I learned the hard way a week ago that when you do an mtn update and gives you a choice between branches, it can be a better idea just to wait and update again after they are merged back in Jul 16 20:50:12 is there two branchs actually ? Jul 16 20:50:18 you mean the folder for config and tmp and all? Jul 16 20:50:24 yes Jul 16 20:50:41 tutorial use a folder on the root, but i have more free space on my home partition Jul 16 20:50:46 I think that during development at times you may try to pull and update when it is being worked on an the changes haven't been merged back, so it may give you an option Jul 16 20:51:00 don't pick a fork, just wait and try again later after it has been merged back in Jul 16 20:51:15 it shouldn't matter where you put it as long as you have write access Jul 16 20:51:19 and as long as you have enough space Jul 16 20:51:29 if you want to you can always just make a symbolic link to somewhere else Jul 16 20:51:37 don't run as root, btw :P Jul 16 20:51:56 i must be root to create a folder on root Jul 16 20:51:57 xDD Jul 16 20:52:07 angstrom is a security focus :P Jul 16 20:54:00 make a folder on root and then chmod it to make it writeable by your user Jul 16 20:54:17 or use a gui file manager as root to change permissions and all as you see fit Jul 16 21:57:07 hi Jul 16 21:57:52 hi Jul 16 22:22:22 does a guide exist (for the ipaq h4300) that shows how to backup the WM OS before installing angstrom, for restoring it at a later time? Jul 16 22:24:02 you may be able to use the info at familiar.handhelds.org for that Jul 16 22:24:06 I believe they have a backup guide Jul 16 22:24:27 its not angstrom, but you are probably just backing up raw bits so it would be fine Jul 16 22:24:55 mscdex: you don't need to "backup WM OS". you need to backup your data. Jul 16 22:27:32 where is that done? Jul 16 22:28:00 mscdex: read your device manual Jul 16 22:45:34 i meant backing up the flash rom. i read the h2200 install guide and it shows this, but is the process similar enough to use on the h4000? Jul 16 22:46:43 I didn't back up mine because apparently rom images for many of the ipaqs are on the familiar linux site Jul 16 22:46:54 and I really don't care for the ppc either way Jul 16 22:46:55 :D Jul 16 22:48:06 they're on the familiar site? the only reason I wish to make a backup is in case I want to sell off the device later on down the road Jul 16 23:57:54 is there a specific package for binutils-symlinks? Jul 17 00:58:44 is anyone around? Jul 17 00:59:03 Nope Jul 17 00:59:32 NAbyss: do you know anything about binutils-symlinks or cfdisk being in OE? Jul 17 01:00:01 Nope Jul 17 01:01:32 alright, hrm Jul 17 01:56:53 grrr Jul 17 01:57:31 someone broke kernel build at least for h2200.. again Jul 17 01:57:44 In file included from arch/arm/mach-pxa/h2200/h2200.c:55: Jul 17 01:57:45 include/linux/soc/hamcop_base.h:29: error: field 'gpiodev_ops' has incomplete type Jul 17 01:57:48 include/linux/soc/hamcop_base.h:38: error: two or more data types in declaration specifiers Jul 17 01:57:52 FATAL: oe_runmake failed **** ENDING LOGGING AT Tue Jul 17 02:59:59 2007