**** BEGIN LOGGING AT Sun Aug 12 02:59:59 2012 Aug 12 08:46:56 hi, has anyone had problems sending to the openembedded-devel mailing list over the past 12 hours or so? Aug 12 08:49:39 yes Aug 12 08:50:05 rulz--: send your emails to openembedded-core@lists.linuxtogo.org Aug 12 08:50:17 and openembedded-devel@lists.linuxtogo.org Aug 12 08:51:17 ok, thanks. Aug 12 08:51:52 found a bug with the relocateable sdk setup for a qt toolchain Aug 12 08:52:26 that's probably for oe-core ML then oe-devel Aug 12 10:13:14 morning Aug 12 10:19:44 hi all Aug 12 10:20:17 i seem to be missing something essential.. still not able to even build core-image-minimal .. Aug 12 10:20:53 udev/systemd issues it seems.. now trying with just the minimal amount of layers (just oe-core and meta-tomtom) Aug 12 10:21:41 ERROR: Error executing a python function in /home/gmc/src/oe-tomtom/meta-openembedded/meta-oe/recipes-core/udev/udev_182.bb: Aug 12 10:21:44 OSError: [Errno 2] No such file or directory: '/home/gmc/src/oe-tomtom/build/tmp-eglibc/work/armv4t-oe-linux-gnueabi/systemd-git-r5/packages-split/libgudev' Aug 12 10:21:53 which is right, there is no libgudev, but there is a libgudev-1.0 Aug 12 10:22:03 (this was with meta-openembedded/meta-oe in bblayers) Aug 12 10:27:49 ah.. managed to build core-image-minimal.. so what is wrong with adding meta-oe to bblayers? is it all or nothing with meta-openembedded? Aug 12 10:29:48 gmc: meta-oe adds newer version of udev, apparently this has some compatibility issues it would seem Aug 12 10:30:23 you can just set PREFERRED_VERSION_udev = "164" Aug 12 10:30:35 ah of course Aug 12 10:30:51 not that i need meta-oe at the moment i think.. Aug 12 10:31:06 what's meta-tomtom? is this a public layer? Aug 12 10:31:14 well it's my current experiment Aug 12 10:31:22 ah ok Aug 12 10:31:35 https://github.com/sonologic/meta-tomtom Aug 12 10:31:50 not much in there yet, apart from the kernel patches from tomtom Aug 12 10:32:14 i want to port that to linux 3.4, but decided to start with something i know to work Aug 12 10:36:55 btw, is the advised way to build a kernel with initrd image backed in still to have two kernel recipes?? one pre-kernel that allows the image to be built, and then one that builds the kernel with the initrd image in it? Aug 12 10:37:43 if you're using something like kexec I would imagine so yes, since you probably want the kernel for the initrd to have a much more minimal configuration Aug 12 10:38:28 i'm intending (not for the tomtom project, but the other) to run off the initrd, no pivotroot or kexec involved Aug 12 10:38:56 ah ok... well I can't see why you'd really need two recipes in that case Aug 12 10:39:14 well, to build the image, one needs the kernel/kernel modules built, right? Aug 12 10:39:36 but if you don't have the image yet, you can't build the kernel.. oh wait.. something about different stages probably :) Aug 12 20:26:57 How do I get psplash working in oe-core (angstrom) ... it does'nt fire up automatically ? **** ENDING LOGGING AT Mon Aug 13 02:59:58 2012