**** BEGIN LOGGING AT Tue Jul 24 02:59:58 2012
Jul 24 07:07:27 <dxtr> Let's say I want to cross-compile X and it has a gazillion dependencies. Can I somehow, within the toolchain, use opkg to install those dependencies on the machine I'm building on? That is an x86_64 and I want to compile for the beaglebone
Jul 24 07:07:43 <dxtr> Or do I really have to compile all those dependencies first?
Jul 24 10:38:50 <bsder> So, I followed the instructions here: http://www.angstrom-distribution.org/building-angstrom
Jul 24 10:39:12 <bsder> If I try the console-image, it won't let me log in ...
Jul 24 10:39:26 <bsder> It does, however, work for just systemd-image ...
Jul 24 10:40:06 <bsder> However, when I build that, my uname is: Linux beaglebone 3.2.18 #1 Sun Jul 22 06:32:43 PDT 2012 armv7l GNU/Linux
Jul 24 10:40:47 <bsder> Then, if I run an opkg update; opkg upgrade, my uname is: Linux beaglebone 3.2.23 #1 Tue Jul 17 10:32:22 CEST 2012 armv7l GNU/Linux
Jul 24 10:41:07 <bsder> So, my question:
Jul 24 10:41:31 <bsder> Why does the repo build 3.2.18?  Shouldn't it build 3.2.23?
Jul 24 23:06:12 <spacecolonyone> what is the proper bitbake recipe/ depends for me to add to my image to use real utilities instead of busybox?
Jul 24 23:07:38 <spacecolonyone> for instance my routine table is hosed, and whereas i know the traditional command to fix it, busy box doesn't support the -interface option, and doesn't document the command either
Jul 24 23:11:39 <spacecolonyone> On a related note, this build pulls an ip and wired networking works perfectly with a USB adapter at one location, when I travel to our other lab, it doesn't behave properly at all. There is something about the the network configuration (which is typical as far as I know how to tell) at this location that does not play well with the routing tables
Jul 24 23:28:01 <spacecolonyone> so I temporarily fixed it by doing "rmmod smsm95xx"
**** ENDING LOGGING AT Wed Jul 25 02:59:58 2012