**** BEGIN LOGGING AT Mon Jul 04 02:59:58 2011 Jul 04 08:28:52 morning all Jul 04 14:44:26 RP__: any chance oe-core kernel.bbclass get fully in synch with oe-dev? Jul 04 14:44:43 ant_work: Nobody has sent patches... Jul 04 14:45:03 I lack the initramfs bits atm Jul 04 14:47:23 RP__: I'm having hard times with klibc. As it is the recipe builds against linux headers (it is possible to build against linux-libc-dev, debian does, but that's next step). Jul 04 14:48:00 now, in oe-dev I could peek at the ARCH kernel headers while NOT having machine-specific package Jul 04 14:48:14 this seems impossible (at first try) in oe-core Jul 04 14:51:49 RP__: sorry, firefox5 did OOM Jul 04 14:52:40 RP__: I mean "${STAGING_DIR}/${MACHINE_ARCH}${TARGET_VENDOR}-${TARGET_OS}/kernel" Jul 04 14:53:05 in oe-dev was the trick Jul 04 14:53:58 now, in oe-core I have to use STAGING_KERNEL_DIR Jul 04 14:56:21 ant_work: Those files are machine specific in oe-dev though? Jul 04 15:01:29 no, I could apply this hack and they are ARCH specific Jul 04 15:02:08 ah, you mean the headers? Jul 04 15:08:09 RP: I was 'inspired' by http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-June/020773.html Jul 04 15:17:26 ant_work: STAGING_KERNEL_DIR is machine specific in both oe-dev and oe-core Jul 04 15:17:44 ant_work: You can pretend otherwise but it can contain machine specific files Jul 04 15:20:31 ok, then will be machine-specific until is beaten to build against linux-libc-headers **** ENDING LOGGING AT Tue Jul 05 02:59:57 2011