**** BEGIN LOGGING AT Tue Jan 15 02:59:58 2013 Jan 15 06:34:19 I'm trying to do an Angstrom build as per 'http://www.angstrom-distribution.org/building-angstrom' (systemd_gnome_image target) and getting 'No package 'libudev' found' errors from the systemd_git or libatasmart packages Jan 15 06:39:09 thinking the problem might be related to this patch 'http://www.mail-archive.com/openembedded-devel@lists.openembedded.org/msg29217.html' Jan 15 18:42:35 when following this guide: http://www.angstrom-distribution.org/building-angstrom Jan 15 18:42:42 how do i know which kernel version it's going to build? Jan 15 18:44:39 how do i find out, rather? Jan 15 18:44:51 what machine are you building for? Jan 15 18:45:06 beagleboard Jan 15 18:45:32 look in meta-ti in the conf/machine directory Jan 15 18:45:38 and read the beagleboard file Jan 15 18:45:51 also try bitbake virtual/kernel and see what it buidls Jan 15 18:46:07 i don't have a conf/machine directory Jan 15 18:46:16 what is in there Jan 15 18:46:32 grep linux -r meta-ti -r Jan 15 18:46:32 auto.conf Jan 15 18:46:32 bblayers.conf Jan 15 18:46:32 local.conf Jan 15 18:46:32 site.conf Jan 15 18:47:54 grep: meta-ti: No such file or directory Jan 15 18:48:12 look around some Jan 15 18:48:41 i have sources/meta-ti Jan 15 18:51:29 i have sources/meta-ti/conf/machine/beagleboard.conf, but i see nothing in there to indicate kernel except MAHINE_FEATURES = "kernel26 ..." Jan 15 18:51:40 *MACHINE_FEATURES Jan 15 18:52:11 hokay. Jan 15 18:52:41 zzzzz.... Jan 15 18:52:56 PREFERRED_PROVIDER_virtual/kernel = "linux-mainline" Jan 15 18:53:42 am supposed to extrapolate from intuition what that's supposed to mean? Jan 15 18:53:45 am i Jan 15 18:54:43 I am doing work Jan 15 18:54:58 but that would suggest the kernel comes from a recipe called linux-mainline Jan 15 18:55:17 but you might see soemthing else, since the angstrom script shoulds use a sable branch Jan 15 18:59:47 Crofton|work: ok, well thanks. Jan 15 23:15:53 what is virtual/kernel ? Jan 15 23:16:01 is it a directory path? Jan 15 23:16:14 i.e., as used here: http://www.slimlogic.co.uk/2011/05/openembeddedangstrom-kernel-workflow/ Jan 15 23:25:57 its a build target Jan 15 23:26:54 http://www.yoctoproject.org/docs/1.3/poky-ref-manual/poky-ref-manual.html#usingpoky-components-bitbake Jan 15 23:27:19 I've just built my first kernel too, Yates, so I'm about 0.5 steps ahead of you. Jan 15 23:29:03 the steps in that building angstrom document do work… it just takes a dang long time to build Jan 15 23:30:36 yates: where are you in the world? Jan 15 23:32:23 toneeee, make sure you enable that parallel build options Jan 15 23:34:31 yeah. I will /now/. My first build attempt was laughable because my default install account has a ulimit -u of 35 and so I thus had a lot of build failures due to the build process needing more than 35 procs to build many packages. Now that I have fixed ulimit, I can roll on out with the paralle Jan 15 23:34:34 parallel Jan 15 23:35:06 well no wonder it took so long! Jan 15 23:35:08 yeap Jan 15 23:35:20 anyway, just a foible Jan 15 23:35:33 not a complaint to this group at all, I guess. Jan 15 23:36:49 * XorA is quite surprised those instructions still work actually Jan 15 23:38:37 Well I know some of you have done your best to keep up the help here and on other web resources like blogs, or the google groups… I'm not yet in a position to write doc about something I don't yet understand fully. This Workflow document is really hot: http://www.slimlogic.co.uk/2011/05/openembeddedangstrom-kernel-workflow/ Jan 15 23:38:52 toneeee: I wrote it Jan 15 23:39:00 THANK YOU!!!! Jan 15 23:39:15 3-4 years ago now Jan 15 23:39:21 Nothing else has explained how to do this work as well as that Jan 15 23:41:26 I use a remote Centos6 build environment and a Mac for my local desktop … had to get an ext2/3 driver for my mac to be able to deploy the rootfs tarball. I just set up the ext2 driver before I connected, so I will try the kernel/rootfs in just a few. Jan 15 23:42:22 All in all it's a "good" experience compared to other work I've done in the *nix world. Thanks a ton for your docs and other efforts, sirs. Jan 15 23:42:58 I was doing a contract and just wrote what I was doing! Jan 15 23:48:28 I'm about to go write a driver for the DMTimers in the Beaglebone. I'm wondering if anyone else is doing it so I don't run at cross-purposes to their work or accidentally recreate a wheel Jan 15 23:49:24 I've looked a /lot/ for something like a DMTimer driver but I can't say I have looked everywhere. I know the Timers work great because the kernel uses them, but there's no userspace driver and I think I have an okay design for a sysfs interface to them. Jan 16 00:12:37 toneeee, might check in #beagle Jan 16 00:13:05 coldsoup, thank you **** ENDING LOGGING AT Wed Jan 16 02:59:59 2013