BBB angstrom building BBB angstrom - oebb.sh script errors

I’m trying to use the BBB to build it’s own software using a usb hdd.

I started with the instructions form here:
http://www.angstrom-distribution.org/building-angstrom

git clone git://github.com/Angstrom-distribution/setup-scripts.git
works fine.

I’m guessing that the right machine name for the BBB is the same as the BBW = beaglebone.
Can anyone confirm that is the right name to be using?

MACHINE=beaglebone ./oebb.sh config beaglebone
quickly dies due to this test in the script:

if ! git help log | grep -q no-abbrev ; then
echo “Your installed version of git is too old, it lacks --no-abbrev. Please install 1.7.6 or newer”
exit 1
fi

That bit of code seems to be using the presence of “no-abbrev” in the git docs as a proxy decision for the installed git version. I’m thinking that will always fail on the BBB as
git help log
(when run on the BBB ) results in:
No manual entry for git-log

Since git --Version tells me that git is 1.7.7, I commented out the “troublesome” test and forged ahead.

MACHINE=beaglebone ./oebb.sh update
tries to run - but fails with
Processing meta-xilinx: Fetching origin
updating to d196fa93c7ff5e080d4c44e2b83aed472f32b2c7
fatal: Could not parse object ‘d196fa93c7ff5e080d4c44e2b83aed472f32b2c7’.

I’d like to know two things:

  1. can the BBB anstrom package be built with the BBB?
  2. If so, Where can I find the right incantations to do so?

Dave

Hi DaveCVI,

From greping the scripts, I have deduced that the name of the BBB is beaglebone-black.

I have tried to build Angstrom from Debian (Linux debian7 3.2.0-4-amd64 #1 SMP Debian 3.2.46-1 x86_64 GNU/Linux) and from Ubuntu (Linux ubuntu 3.5.0-23-generic #35~precise1-Ubuntu SMP Fri Jan 25 17:13:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux) and in both cases the process fails on the command:

MACHINE=beaglebone-black ./oebb.sh config beaglebone-black

Like you, I get the error message:

Processing meta-xilinx: Fetching origin
updating to d196fa93c7ff5e080d4c44e2b83aed472f32b2c7
fatal: Could not parse object ‘d196fa93c7ff5e080d4c44e2b83aed472f32b2c7’.

I went back and tried to build Angstrom for the plan beagleboard and got the same result. For what it’s worth, this procedure worked on Monday, but not now.

Note: I was using git 1.7.10.4 (Debian) and 1.7.9.5 (Ubuntu).

So at this point I would suggest that the problem is unrelated to trying to run this on the BBB itself, but may be caused by some fault in the git repository?

Regards,

jhalsopiv

I tried your ‘MACHINE=beaglebone-black’ instead of ‘MACHINE=beaglebone’ and got an error for invalid MACHINE (I am building on ubuntu-12.4):

export MACHINE=beaglebone-black
./oebb.sh config beaglebone-black
./oebb.sh update

./oebb.sh bitbake cloud9-gnome-image


Using /home/jlf/.oe/environment-angstromv2012.12 to setup needed variables. It is recommended to do ‘. /home/jlf/.oe/environment-angstromv2012.12’ and run ‘bitbake something’ without using ./oebb.sh as wrapper
Executing: MACHINE=beaglebone-black bitbake cloud9-gnome-image
Pseudo is not present but is required, building this first before the main build
ERROR: OE-core’s config sanity checker detected a potential misconfiguration.
Either fix the cause of this error or at your own risk disable the checker (see sanity.conf).
Following is the list of potential problems / advisories:

Please set a valid MACHINE in your local.conf or environment

ERROR: Execution of event handler ‘check_sanity_eventhandler’ failed

Jim

I have tried ‘MACHINE=beaglebone’, ‘MACHINE=beagleboard’, and ‘MACHINE=beaglebone-black’ and in each case I cannot get past the config step, e.g.

export MACHINE=beaglebone
./oebb.sh config beaglebone

I always end up with:
Processing meta-xilinx: Fetching origin
updating to d196fa93c7ff5e080d4c44e2b83aed472f32b2c7
fatal: Could not parse object ‘d196fa93c7ff5e080d4c44e2b83aed472f32b2c7’.

So you are already farther along than I am. When I solve the fatal error problem, I can look forward to this next obstacle. Have you had any luck trying to build for the beaglebone rather than the beaglebone-black?

Yes, one time with ‘MACHINE=beaglebone’ I got all the way through ‘./oebb.sh bitbake cloud9-gnome-image’. Lots of warnings, but no errors. And the resulting rootfs did not match the one in the downloaded latest “BBB-eMMC-flasher-2013.06.20.img.xz” from http://beagleboard.org/latest-images.
That’s why I posted “[BBB] Am I building the latest Angstrom image right?” asking what MACHINE should be and what image I should be building to match what’s on the latest-images site.

Jim

i made some changes to layers.txt to avoid errors, but still can’t build

bitbake,https://github.com/openembedded/bitbake.git,master,7e3a99949358f4362876df5a82f8aeaae72c3c97
meta-angstrom,https://github.com/Angstrom-distribution/meta-angstrom,angstrom-v2012.12-yocto1.3,HEAD
meta-openembedded,https://github.com/Angstrom-distribution/meta-oe.git,angstrom-staging-yocto1.3,HEAD
meta-beagleboard,https://github.com/beagleboard/meta-beagleboard.git,master,HEAD
meta-ti,https://github.com/Angstrom-distribution/meta-ti.git,angstrom-staging-yocto1.3,HEAD
meta-ettus,https://github.com/balister/meta-ettus.git,master,5a6a642f6707dc42a5210dbbf01d2bdfd869d4b0
meta-efikamx,https://github.com/kraj/meta-efikamx.git,master,07f2a5c777b4f866985735303bc6d696592760a9
meta-nslu2,https://github.com/kraj/meta-nslu2.git,master,8948458fe3ec2b3c713b2a13a87123b64e22b0d9
meta-smartphone,http://git.shr-project.org/repo/meta-smartphone.git,danny,HEAD
meta-intel,https://git.yoctoproject.org/git/meta-intel,danny,98342e9e685ac8066f7fe2517fd382127a286648
meta-xilinx,https://git.yoctoproject.org/git/meta-xilinx,master,31b1ec743cc0c6484c426bc7e1621a0608f0a1ea
meta-openpandora,https://github.com/openpandora/meta-openpandora.git,master,bdd973321efabf9da4ac7bbc5e18ecab257841a3
meta-raspberrypi,https://github.com/djwillis/meta-raspberrypi.git,danny,HEAD
meta-handheld,http://git.openembedded.org/meta-handheld,danny,HEAD
meta-opie,https://github.com/bluelightning/meta-opie.git,master,c242efc6ca55772a88602f1f8f94dff697b38430
meta-java,https://github.com/woglinde/meta-java.git,master,75dee76c7cfbf1418e5c581f50bb57b3282013f7
meta-browser,https://github.com/OSSystems/meta-browser.git,danny,HEAD
meta-mono,https://git.yoctoproject.org/git/meta-mono.git,master,adf47f078dbf788a80ff1398a15a4fd5a334d320
meta-kde,https://git.gitorious.org/openembedded-core-layers/meta-kde.git,master,316d9c27e72cfebc7618268f8766624ee3f5e18e
meta-linaro,https://git.linaro.org/git-ro/openembedded/meta-linaro.git,danny,HEAD
meta-minnow,https://git.yoctoproject.org/git/meta-minnow,danny,HEAD
meta-allwinner,https://github.com/naguirre/meta-allwinner.git,danny,HEAD
meta-ros,https://github.com/bmwcarit/meta-ros.git,master,430f67cdd8c3b54270a08a2921083843406b4f74
openembedded-core,https://github.com/Angstrom-distribution/oe-core.git,angstrom-staging-yocto1.3,HEAD

I’ve run into a couple of build issues…haven’t worked on them enough to solve just yet:

  • makeinfo got upgraded, and this causes a build issue with linaro-gcc (build failure occurs on Debian Jessie & Fedora19)
  • nodejs failed to build with an error which effectively meant path too long

One thing you might try to ‘fix’ the meta-xilinx issue you’re seeing is remove the ~/.oe/environment* file (or save it somewhere else) and re-run the initial config steps…I did run into a random issue where setup-scripts picked up a different branch than master, and that caused issues. I have no idea quite how it did that.

-Dale

I’m running into this problem this weekend. Were any of you able to figure out what was going wrong? It definitely seems like it’s something wrong with the repo, or maybe the OpenEmbedded glue that holds it all together?

Would greatly appreciate any insight you all had after (presumably) getting past this issue.

Lee

First of all, I have not seen the "git" error. My version of git is 1.7.10.4.

Secondly, I too get the error in the xilinx fetch. I presume it is pegged to a removed commit. God only knows why! Anyway I have just ignored that "fatal" message and continued with:

. ~/.oe/environment-angstromv2012.12
bitbake systemd.image

or your favorite image recipe :wink:

This seems to work OK. There still appear to be some warnings, but the resulting images work well on both BBB and BBW.

HTH,

Dave L.

Correction - bitbake systemd-image

First of all, I have not seen the "git" error. My version of git is
1.7.10.4.

Secondly, I too get the error in the xilinx fetch. I presume it is pegged
to a removed commit. God only knows why! Anyway I have just ignored that
"fatal" message and continued with:

. ~/.oe/environment-angstromv2012.12
bitbake systemd.image

As best I can tell based on some IRC discussion over the weekend, 2012.12
no longer builds due to changes in dependent repositories. You'll need to
try 2013.06. You should probably check the angstrom developer mailing list
for the history.

How do I get 2013.06? Performing the steps on the Angstrom developer page (http://www.angstrom-distribution.org/building-angstrom) still gets me 2012.12

Regards,

Dave.