I chose the 32 bit version because I read a note about some stuff not working on 64 bit:

"Please note pysco is only available for 32-bit x86 systems only."

From: Alex Gibson <alxx@alexthegeek.com>
To: General mailing list for gumstix users. <gumstix-users@lists.sourceforge.net>
Sent: Wed, December 8, 2010 1:02:08 AM
Subject: Re: [Gumstix-users] Please help--I'm unable to get a build environment working

On 8/12/2010 3:44 PM, Darren wrote:
OK I'm going to try a from scratch (4th time!) install.  I'm a little frustrated right now.  I've been using Linux since Linus was in college and you got distros on floppies.  I feel like there should be a 100% clear set of instructions (i.e. a cold-start procedure) that any first time user will be able to ace, let alone a 20 year veteran.  So in the interest of developing those instructions I will log my all of my steps and post to the list anytime there is an error or question.  

I am going to start a fresh ubuntu 10.10 i386 32 bit install in the latest virtualbox on my quad core windows vista 64 bit machine.  I will give the VM 512 MB of ram and a dynamic 60 Gig hard virtual hard drive formatted with ext4.

I'm choosing standard USA defaults and a username of dhumphre.

OK the virtualbox image is installed and booted.

I'm logging in as dhumphre and opening a terminal.  I will start by following the instructions on http://wiki.openembedded.net/index.php/OEandYourDistro#Debian 

OK. So here's the first point in the instructions that are not 100% unambiguous:

Should I do this:  "The easiest way is via apt-get'able Openembedded which will pull the OE meta-data for you and keep it up-to-date."  

Or should I follow the directions and do: 
"aptitude install sed wget cvs subversion git-core \
   coreutils unzip texi2html texinfo docbook-utils \
   gawk python-pysqlite2 diffstat help2man make gcc build-essential g++ \
   desktop-file-utils chrpath

Why 32 bit ?
Around 3GB is the sweet spot for ram(set 3.6GB and dual core on our build vm's on our vm servers)

Follow the directions.
Make sure to do the sourcing properly. Then reboot or open a new terminal before trying to run bitbake.
I tend to do both option a and b for sourcing.

Once you've got it working edit /user/overo/build/site.conf
uncomment Parellel_MAKE and BB_NUMBER_THREADS
to get a speed up on a machine with multiple cores/processors.


UTS CRICOS Provider Code: 00099F
DISCLAIMER: This email message and any accompanying attachments may contain confidential information. If you are not the intended recipient, do not read, use, disseminate, distribute or copy this message or attachments. If you have received this message in error, please notify the sender immediately and delete this message. Any views expressed in this message are those of the individual sender, except where the sender expressly, and with authority, states them to be the views the University of Technology, Sydney. Before opening any attachments, please check them for viruses and defects.