**** BEGIN LOGGING AT Tue Jul 12 02:59:57 2011 Jul 12 05:49:58 Hi, am I doing something oviously stupid if i cannot get .so but only a static lib out of libharu? Recipe: http://nopaste.voric.com/paste.php?f=u648gv Jul 12 05:55:19 In sysroots dir however i do have an arm .so Jul 12 07:41:16 Anyone had problems with udev 171 compilation? (extras/input_id/input_id.c:167:24: error: 'BTN_TRIGGER_HAPPY' undeclared (first use in this function)) Jul 12 08:08:31 * rschus is reminded of http://www.youtube.com/watch?v=6S71bzLtf98 by BTN_TRIGGER_HAPPY ;) Jul 12 08:22:09 morning all Jul 12 09:08:36 Hi everybody Jul 12 09:08:51 Can I build android with OE? Jul 12 09:09:30 I checked recipes and found android-image-utils-native_git.bb file, but it is not and image bb Jul 12 09:09:52 does this mean I can not build android with OE? Jul 12 10:18:03 yes, that pretty much means it. noone bothered to add android to OE yet Jul 12 10:18:31 most smartphone action in OE is centered around completely free systems (for whatever that means is disputable, i know) Jul 12 11:01:30 Where can I set the kernel for virtual/kernel? Jul 12 11:01:33 PREFERRED_PROVIDER_virtual/kernel = "linux-omap-psp" seems not to work anymore Jul 12 11:17:04 OK, found it: the distro file overrides PREFERRED_PROVIDER_virtual/kernel Jul 12 12:02:14 Uncompressing Linux... done, booting the kernel. Error: unrecognized/unsupported machine ID (r1 = 0x0000065a).Available machine support: ID (hex) NAME 000009d8 MINI6410 Please check your kernel config and/or bootloader. Jul 12 12:02:46 hey guies i got this error at gtk term Jul 12 12:04:08 i was cross compiling the kernel for mini 6410 , i sucessfully cross compiled it but it gives this error on board Jul 12 12:04:24 any one whohas got this error? Jul 12 14:26:23 Can anyone build texinfo on oe-core (and only oe-core) ? Jul 12 14:27:39 I'll give it a go. Jul 12 14:30:39 It built ok, though I have a few QA ISSUEs. Jul 12 14:32:22 hi pb_, Tartarus Jul 12 14:33:17 qemux86 or other/ Jul 12 14:33:25 and do you have zlib.h installed system-wide/ Jul 12 14:33:34 stupid vmware console plugin eats my shift keys Jul 12 14:33:46 epia (i586), and yes Jul 12 14:35:17 i bet that's why it works, heh Jul 12 14:36:11 I'll remove zlib1g-dev and try again Jul 12 14:43:41 question for you guys, oe-core QA found out th eklibc-utils are stripped before install. Strange I never noticed the QA in oe-dev Jul 12 14:44:42 in fact they are processed right after build http://git.kernel.org/?p=libs/klibc/klibc.git;a=blob;f=scripts/Kbuild.klibc Jul 12 14:44:50 yeah, now it fails, zlib.h not found Jul 12 14:45:31 looks like it's missing a dependency on zlib-native Jul 12 14:45:37 (it has zlib in there but not the -native one) Jul 12 15:13:29 ant__: heh, oh yes. Jul 12 15:13:42 those krazy klibc h4x0rs Jul 12 15:16:16 maybe the QA for such cases was shut up in oe-dev? Jul 12 15:17:06 yeah, or possibly oe.dev just never had that check. I don't remember. Jul 12 15:17:31 iirc in May 2010 a big cleanup wrt strip was done Jul 12 15:17:58 maybe check has been disabled afterwards Jul 12 16:19:47 pb_: the question is purely achademic here, being there are no -dbg packages atm Jul 12 16:20:20 actually, packaging is a disaster :/ Jul 12 16:26:54 ok, moving to beach now, bbl Jul 12 18:14:37 Is there a supported way of referencing another recipe's build tree? Jul 12 18:15:18 don't do that. Jul 12 18:15:40 there's no way at all, period. If something needs to be shared, you'll have to install it into the sysroot and have the other recipe get it from there Jul 12 18:16:09 I want to build a qt plugin that needs generated files in the original qt build Jul 12 18:17:59 (which don't end up in the sysroot) Jul 12 18:21:52 then either you'll need to include the qt sources and regenerate those files, or install them into a private area in the sysroot Jul 12 18:22:03 the sysroot is *the* mechanism to access the files of one recipe from another Jul 12 18:22:03 ok Jul 12 18:24:37 I would add these needed files to qt-dev Jul 12 22:06:46 sgw: ping? Jul 12 22:06:54 Or, anyone that runs the oe-core tests? Jul 12 22:07:49 tests? Jul 12 22:08:04 Tartarus: I am around, but unavailable for 30 minutes or so. Jul 12 22:08:08 k Jul 12 22:08:13 I'll dig a bit deeper for 30min, thanks :) Jul 12 22:08:50 good nite Jul 12 22:38:17 Tartarus: I am back, what are you looking for? Jul 12 22:38:46 I wanna know how to easily run some of the tests you guys have, if possible Jul 12 22:38:51 vs qemux86 Jul 12 22:39:06 The autobuilder tests? Jul 12 22:39:11 yeah Jul 12 22:39:16 doing some siteinfo updates Jul 12 22:39:20 and wanna make sure stuff is sane Jul 12 22:39:41 hang on, have to refresh those bits Jul 12 22:40:59 k Jul 12 22:44:20 Tartarus: I am looking at what the autobuilder does for the sanity tests, and it seems you need to do a "bitbake core-image-minimal -c qemuimagetest", But there may be some more setup that is needed. Jul 12 22:45:00 k Jul 12 22:45:04 that'll get me started, thanks Jul 12 22:45:13 Aha, it is in the wiki: https://wiki.yoctoproject.org/wiki/Enabling_Automation_Test_in_Poky Jul 12 22:45:56 Tartarus: let us know if that all work, if not we can have the QA folks do an update on it. Jul 12 22:46:03 k, will do Jul 13 01:19:17 linux-input seems to be seeing a build failure with jstest, http://build.sakoman.com/public/logs/task/57357.txt Jul 13 01:30:40 huh, didn't realize libvirt supports lxc containers **** ENDING LOGGING AT Wed Jul 13 02:59:56 2011