I’m running on a kubuntu 13.10 system and trying to build an Angstrom image for a BeagleBone Black. I’ve used the instructions at http://www.elinux.org/Beagleboard:BeagleBoneBlack_Rebuilding_Software_Image to try to duplicate the system that ships with the board.
I can build the systemd-image, cloud9-image and virtual/kernel, but when I try to build the cloud9-gnome-image I always get the following error:
ERROR: Nothing RPROVIDES ‘update-modules’ (but /home/gwilson/open-embedded/sources/meta-ti/recipes-ti/dsplink/ti-dsplink_1.65.00.03.bb, /home/gwilson/open-embedded/sources/meta-ti/recipes-ti/local-power-manager/ti-local-power-manager_1.24.02.09.bb RDEPENDS on or otherwise requires it)
I’ve tried building the cloud9-gnome-image image after building other images and also in a new repository just after building virtual/kernel. Here are the steps that I’ve gone through most recently:
git clone git://github.com/Angstrom-distribution/setup-scripts.git open-embedded
cd open-embedded/
MACHINE=beagleboard ./oebb.sh config beagleboard
there is a message during this step about being able to use environment-angstrom-v2013.12 instead of oebb.sh
MACHINE=beagleboard ./oebb.sh update # everything was up to date, or fixed to revision
echo “export MACHINE=beagleboard” >> ./environment-angstrom-v2013.12 # to fix beaglebone as the target that I want
. environment-angstrom-v2013.12 # source the environment so as not to need oebb.sh
bitbake cloud9-gnome-image -c populate_sdk
and then I get the error, the -c populate_sdk makes no difference.
I’ve searched for this error and found a post on a Gumstix mailing list that addresses the same problem with a response pointing to a set of changes in a private branch of meta-ti at https://github.com/scottellis/meta-ti with the message that what’s relevant are the last 2 patches. Could this be a problem that the code that I’m trying to build is fixed to a previous revision or do I have some other build system or configuration problem?
As a last test of my installation I tried building again from a completely new pull of the code, but this time instead of sourcing environment-angstrom-v2013.12 I used the MACHINE=beagleboard ./oebb.sh bitbake cloud9-gnome-image -c populate_sdk. I get the same error.
Any help that anyone could give me would be greatly appreciated.
Greg