If in your GSoC you are targeting angstrom and are having problems with it, please post them to this list so we can resolve them. And now the important bit:
if someone suggests using the stable/2009 branch, do NOT listen to them and ignore any angstrom or OE advice they are giving, it is most likely a year behind.
When the beagleboard xM launches next month it will ship with an angstrom demo image built from .dev and I'm trying to get that same image shipped with C5 boards, so please don't target anything as outdated as stable/2009.
So if you are following http://www.angstrom-distribution.org/building-angstrom take the "something newer" option that leads you to http://gitorious.org/angstrom/angstrom-setup-scripts . The script in there is what I use and what we are deploying inside TI as well.
I've made a post on my blog about my OE setup on Ubuntu 10.04 and the
errors I ran into while building nano and console-image from the dev
branch, and how I attempted to overcome them, at
There is one thing I'd like to ask about one of my "solutions". I
deleted all the -native suffixed glib-2.0 recipes to get gtk+ to build
-that's how I interpreted a discussion on the mailing list regarding
this problem, but the discussion itself was not so entry-level. Will
this cause any problems? What is the preferred method of dealing with
That's a symptom of using bitbake 1.8.x. instead of 1.10.x, that's why http://gitorious.org/angstrom/angstrom-setup-scripts is using 1.10. Give that a try. Some general hints:
* do NOT use apt-gettable OE, it's broken by design
* do NOT use apt-get install bitbake, noone installs bitbake, not even the bitbake developers.
* do NOT use the scripts from apt-gettable OE
As you have noticed, using the wrong instructions will lead to lots of problems, which is why http://www.angstrom-distribution.org/building-angstrom exists. The oebb.sh script is nearly completely self documenting, taking care of people who tend to skip bits of instructions.
I am not able to nfs-boot my beagleboard. However, I am able to nfs-mount using busybox. Should I stick to nfs-mount? If not, how do I patch the kernel for longer timeout so that I can nfs-boot my beagleboard?