I abandoned OE long ago and simply use Ubuntu with conventional Gnu tools.  This works rather well both natively and cross compiling.

The only area this lacks in is cross compiling the kernel - for whatever reason I can only get that working using a native compile which is painfully slow.  I pull down the Sakoman omap-2.6.38 git and compile that using the instructions referenced below.  (I use that branch as I also patch the Xenomai real time extensions and there is a very stable patch for 2.6.38 included in Xenomai 2.6.0.)

BTW Xenomai runs very nicely on the Overo once you get it built and installed.

This approach may not work for everyone, but in my shop we support many more platforms than simply Gumstix, so it is very helpful to have a consistent toolchain across platforms.  Plus there was a lot of complaining here about the almost continuous breaking of the OE build, so we simply bailed.

On Tue, Apr 10, 2012 at 11:09 AM, Ash Charles <ash@gumstix.com> wrote:

> Starting with the tool chain:  It seems a bit of a waste for oe to download
> source and build its own tool chain.  After googling around I’ve found that
> the emdebian site has a repository where you can get the tool chain with an
> apt-get.  This works fine for Debian and Ubuntu users.  It would be good
> though, if Gumstix made the tool chain available on their download site in a
> tarball, as well as document how to add the repositories for Debian users.
> (I am happy to help with documentation).
There are a bunch of reasons for building a toolchain from source most
of which I end up not caring about.  For me, I think the easiest and
fastest route to a binary tool chain comes from linaro:
For non-debian (including windows) installers:
For non-Cortex-A bare metal targets (I haven't tested on robovero
but...) https://launchpad.net/gcc-arm-embedded
More details can be found: https://launchpadlibrarian.net/98590974/README.txt
> MLO, u-boot, kernel, kernel modules and root file system:  I got an off-list
> email from Gumstix regarding a request I had made that they put a README
> file on their download site in each of the download directories.  The README
> file would contain info on which kernel version was there, etcetera.
> Another request to Gumstix, could you please put the kernel modules with
> each kernel?  This would make it easier to build a root file system outside
> of oe without having to build the kernel  and its modules.  A sample fstab
> and inittab would be useful as well.
Just a modules.tgz file?  I've added a bug in our internal tracker and
I've mentioned the fstab and inittab though these may be more  of a
> As far as building the kernel goes:  I’ve been trying to figure out where
> the patches are and what kernel they should be applied to, but my only
> source of reference is oe, and the command ‘bitbake virtual/kernel’ doesn’t
> provide a very good starting point.  So another request to Gumstix, could
> you please make the patches available for download as well as a patched
> kernel and a .config file?  And if you’re going to provide a link to another
> site for the patched kernel, then please check that your instructions are
> correct, at the moment they are not.  And also a bit of doco on how to apply
> the patches and do a build.
OE provides the definitive source and patches so providing them
elsewhere will mean they get out of sync.
That said,  I found myself writing these instructions the other day:
"# get a cross compiler
sudo apt-get install gcc-arm-linux-gnueabi
# clone the kernel
git clone git://www.sakoman.com/git/linux-omap-2.6 linux -b omap-3.2
# jump into the repo
cd linux
# setup a default configuration
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- omap3_defconfig
# if you want to make changes..
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- menuconfig
# compile it
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- uImage -j4
You may find 'omap3_defconfig' is not available so use 'omap2plus_defconfig'.
> Which brings us to u-boot, which is a pre-requite to building the kernel.  I
> would appreciate it if someone could help me to get this to build.  When
> I’ve managed to build u-boot and the kernel then I will be happy to write a
> howto on the process.  But I’m struggling at the moment to do something that
> shouldn’t be that hard with the right documentation.
It is certainly not a prerequisite to building the kernel but it is
useful to change the pin-mux'ing etc..  Here is a stab at the steps I
go through:
# get a cross compiler
sudo apt-get install gcc-arm-linux-gnueabi
# clone u-boot
git clone git://www.sakoman.com/git/u-boot.git u-boot -b omap3-v2011.12
# jump into the repo
cd u-boot
# setup a default configuration and compile
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- omap3_overo -j4

Both these instructions require a knowledge of the best branch on
Sakoman's tree from which to be pulling.  I tend to be building for
some specific reason so I'll either know what I'm looking for or will
take the most recently updated one.
> Root file system:  I’ve made and entry in the wiki on building a Debian root
> file system, this is my alternative to Angstrom and oe.  I hope that it is
> useful.
Sweet :).  Thanks.
> The basic build shouldn’t be that hard with a bit of documentation and
> organisation.  It probably seems pretty straight forward to those who know
> how, but coming from the outside it’s not that easy.
Agreed---there are sometimes too many possible ways to do things with
too many possible configurations---finding a reasonable middle ground
is not obvious.  Thanks for the feedback though.

Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
gumstix-users mailing list