Please excuse my very basic question, but I am attempting to build a
system for the "da830-omapl137-evm". I have sucessfully built a root
file system using the online tool, but when I follow the instructions
for building the image on my machine I get the following failure. Just
for experimentation I tried a similar build for "beagleboard" and it
worked fine. I feel that I must be omitting something very fundamental.
I would appreciate any help.
Thanks in advance,
Dave.
dlamb...@development:~$ git clone
git://gitorious.org/angstrom/angstrom-setup-scripts.git
Initialized empty Git repository in
/home/dlambert/angstrom-setup-scripts/.git/
remote: Counting objects: 157, done.
remote: Compressing objects: 100% (144/144), done.
remote: Total 157 (delta 49), reused 0 (delta 0)
Receiving objects: 100% (157/157), 22.20 KiB, done.
Resolving deltas: 100% (49/49), done.
dlamb...@development:~$ cd angstrom-setup-scripts/
dlamb...@development:~/angstrom-setup-scripts$ sh oebb.sh config
da830-omapl137-evm
Unknown machine da830-omapl137-evm, passing it to OE directly
Checking out bitbake
Initialized empty Git repository in
/home/dlambert/angstrom-setup-scripts/sources/bitbake/.git/
remote: Counting objects: 12887, done.
remote: Compressing objects: 100% (3821/3821), done.
remote: Total 12887 (delta 7748), reused 12817 (delta 7708)
Receiving objects: 100% (12887/12887), 2.42 MiB | 1.74 MiB/s, done.
Resolving deltas: 100% (7748/7748), done.
Branch 1.10 set up to track remote branch 1.10 from origin.
Switched to a new branch '1.10'
Checking out OpenEmbedded
Initialized empty Git repository in
/home/dlambert/angstrom-setup-scripts/sources/openembedded/.git/
remote: Counting objects: 400579, done.
remote: Compressing objects: 100% (117692/117692), done.
remote: Total 400579 (delta 277188), reused 395136 (delta 273454)
Receiving objects: 100% (400579/400579), 139.56 MiB | 1.24 MiB/s, done.
Resolving deltas: 100% (277188/277188), done.
Checking out files: 100% (23471/23471), done.
Checking out OE, depending on your git version you might get a harmless,
what git alarmingly calls 'fatal' error. It just means the branch
already exists.
Branch org.openembedded.dev set up to track remote branch
org.openembedded.dev from origin.
Switched to a new branch 'org.openembedded.dev'
Setup for da830-omapl137-evm completed
dlamb...@development:~/angstrom-setup-scripts$ sh oebb.sh update
Updating bitbake
Executing: cd /home/dlambert/angstrom-setup-scripts/sources/bitbake &&
git pull --rebase
Current branch 1.10 is up to date.
Updating OpenEmbedded
Executing: git pull --rebase
Current branch org.openembedded.dev is up to date.
dlamb...@development:~/angstrom-setup-scripts$ source ~/.oe/environment
dlamb...@development:~/angstrom-setup-scripts$ MACHINE=da830-omap137-evm
bitbake base-image ; MACHINE=da830-omap137-evm bitbake console-image
x11-image
NOTE: Handling BitBake files: | (0001/7086) [ 0 %]ERROR: Unable to
determine endianness for architecture 'INVALID'
FATAL: Please add your architecture to siteinfo.bbclass
ERROR: Unable to determine endianness for architecture 'INVALID'
FATAL: Please add your architecture to siteinfo.bbclass
NOTE: Handling BitBake files: | (0001/7086) [ 0 %]ERROR: Unable to
determine endianness for architecture 'INVALID'
FATAL: Please add your architecture to siteinfo.bbclass
ERROR: Unable to determine endianness for architecture 'INVALID'
FATAL: Please add your architecture to siteinfo.bbclass
dlamb...@development:~/angstrom-setup-scripts$
_______________________________________________
Angstrom-distro-users mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
