**** BEGIN LOGGING AT Sun Dec 13 02:59:57 2009 Dec 13 08:41:30 of all the machine options at narcissus/#machinedialog, which one(s) might be x86 compat? Dec 13 08:42:29 would qemux86 be fairly generic? Dec 13 10:30:28 hi Dec 13 11:37:17 can I run internal flash from kexecboot? Dec 13 12:52:56 to answer my own question, yes, qemux86 is indeed ELF 32-bit LSB executable Dec 13 17:40:57 hi, because narcicius didn't build an image I built my own console-image to test angstrom with 256M of ram Dec 13 17:41:03 and there is no: Dec 13 17:41:05 *illume Dec 13 17:41:13 *enlightenment Dec 13 17:41:15 *xfce Dec 13 17:41:17 *xorg Dec 13 17:41:21 in the angstrom feeds Dec 13 17:41:35 so how can I test something? Dec 13 17:41:48 I build with oe.dev for qemux86 Dec 13 17:46:56 GNUtoo: I believe the console-image is very minimal - if you want the packages you listed you should build the xorg-image and then use the opkg to install the ones you are missing - that is what I have done. xorg-image will get you the x server and enlightenment with bits of GPE that are useful on a desktop Dec 13 17:47:37 Analias, I want something working before tomorrow Dec 13 17:48:12 and I had a build failure if I remember well with e-image Dec 13 17:48:42 GNUtoo: if you have OE installed already, the build doesn't take that long - everything built the first time for my platforms (OMAP3 BeagleBoard and Archos Gen6) Dec 13 17:49:48 GNUtoo: a build on my quad core takes about hour for everything the first time Dec 13 17:49:50 ok I'll try again Dec 13 17:50:07 I've only a pentium M 2GHz with heat problems so it runs at less than 2GHz Dec 13 17:52:20 Analias, basically I would have to compile everything,an image,firefox,a mail client etc... Dec 13 17:52:31 because they are not in the unstable angstrom feed Dec 13 17:53:19 you could copy or inherit the xorg-image and include your own dependences - look at the beagleboard-demo-image as an example Dec 13 17:54:28 in fact, other than Illume, I wouldn't be surprised if the beagleboad-demo-image gives you most everything including firefox - it's pretty extensive Dec 13 17:56:17 e-image + bitbake firefox is fine Dec 13 17:56:27 it's only that I wanted to use the angstrom feeds Dec 13 17:56:39 which are nearly empty Dec 13 17:57:19 maybe I miss an url? Dec 13 17:57:23 that was not included Dec 13 17:57:40 because now things have changed Dec 13 17:58:02 there are things like base-feed.conf Dec 13 17:58:16 instead of i686-feed.conf Dec 13 18:01:42 the default feeds that show up under /etc/opkg include most everything - what processor are you building for? Dec 13 18:02:17 nm - I see the i686 - I'm use to building for armv7 or armv4 Dec 13 18:12:08 I'm also used to build for armv4,v6,v6-novfp Dec 13 18:12:21 but...I've to test how angstrom perform with 256M of ram Dec 13 18:12:28 to see if the touchbook is usable Dec 13 18:12:34 before buying one Dec 13 18:13:11 is there a feed specially for graphical things? Dec 13 18:13:21 maybe I should look in my bug device Dec 13 18:16:04 anyway I'm very tired but I remember the faillure was gcc...why does it pull gcc for the target....I mean real gcc not gcc-cross or gcc-native Dec 13 18:17:18 maybe it's just that nothing was built for x86 in the feeds Dec 13 18:17:32 because on my bug device the feed seem the same Dec 13 19:33:43 Anyone of you happen to know if current builds work on Collie? A few months ago the SD and/or CF driver seemed to be broken... Dec 13 20:53:37 !logs Dec 13 20:53:38 Channel logs for #angstrom are archived at: Dec 13 20:53:39 http://hentges.net/tmp/logs/irc/%23angstrom Dec 13 20:53:41 Live-logs are available at Dec 13 20:53:43 http://hentges.net/tmp/logs/irc/livelogs/%23angstrom.livelog Dec 13 20:53:45 See ?? help-logs for usage instructions **** ENDING LOGGING AT Mon Dec 14 02:59:56 2009