Is anybody able to actually BUILD the Angstrom release?

[David Hagood]

On Fri, 2008-12-19 at 13:29 -0500, Cliff Brake wrote:
> Probably means your OE meta dir is not in the BBPATH or BBFILES ...
> 
Evidently having the actual Bitbake dir in the BBPATH was causing this.

> I have my own OE env setup scripts, but just out of curiosity I ran
> through http://wiki.openembedded.net/index.php/Getting_Started, and
> everything seems to work as advertised. 

I have. I get an error on bitbake.

Let's take it from the top:

 ls 
build  cache  download	downloads  openembedded  set_env
ddhagood at sage:/space/OpenEmbedded> ls /space/bitbake-1.8.12/
AUTHORS  ChangeLog  conf     COPYING  lib	PKG-INFO
bin	 classes    contrib  doc      MANIFEST	setup.py
ddhagood at sage:/space/OpenEmbedded> ls /space/OpenEmbedded/openembedded/
classes  contrib      files	   packages  removal.txt
conf	 COPYING.MIT  MAINTAINERS  README    site
ddhagood at sage:/space/OpenEmbedded> unset CDPATH
ddhagood at sage:/space/OpenEmbedded> OE_BASE="/space/OpenEmbedded/"
ddhagood at sage:/space/OpenEmbedded> BITBAKE_BASE="/space/bitbake-1.8.12"
ddhagood at sage:/space/OpenEmbedded>
BBFILES="${OE_BASE}openembedded/packages/*/*.bb"
ddhagood at sage:/space/OpenEmbedded> BBPATH="${OE_BASE}build:
${OE_BASE}openembedded"
ddhagood at sage:/space/OpenEmbedded> 
ddhagood at sage:/space/OpenEmbedded> PATH=$PATH:${BITBAKE_BASE}/bin
ddhagood at sage:/space/OpenEmbedded> 
ddhagood at sage:/space/OpenEmbedded> CACHE="${OE_BASE}cache"
ddhagood at sage:/space/OpenEmbedded> export OE_BASE BBFILES BBPATH CACHE
PATH
ddhagood at sage:/space/OpenEmbedded>  cat build/conf/local.conf
PARALLEL_MAKE="-j2"
BB_NUMBER_THREADS = "2"
DISTRO = "angstrom-2008.1"
MACHINE = "beagleboard"
DL_DIR="${OE_BASE}downloads"
CACHE="${OE_BASE}cache"
ddhagood at sage:/space/OpenEmbedded> cd build
ddhagood at sage:..OpenEmbedded/build>  bitbake task-base
ERROR: no files to build.

NOTE: Parsing finished. 0 cached, 0 parsed, 0 skipped, 0 masked.
NOTE: Cache is clean, not saving.
NOTE: build 200812191308: started
NOTE: <type 'exceptions.IndexError'>:list index out of range while
evaluating:
${@base_detect_branch(d)}
Traceback (most recent call last):
  File "/space/bitbake-1.8.12/bin/bitbake", line 143, in <module>
    main()
  File "/space/bitbake-1.8.12/bin/bitbake", line 140, in main
    cooker.cook()
  File "/space/bitbake-1.8.12/lib/bb/cooker.py", line 644, in cook
    return self.buildTargets(pkgs_to_build)
  File "/space/bitbake-1.8.12/lib/bb/cooker.py", line 531, in
buildTargets
    bb.event.fire(bb.event.BuildStarted(buildname, targets,
self.configuration.event_data))
  File "/space/bitbake-1.8.12/lib/bb/event.py", line 67, in fire
    if tmpHandler(event) == Handled:
  File "tmpHandler(e)", line 31, in tmpHandler
  File "/space/bitbake-1.8.12/lib/bb/data.py", line 97, in getVar
    return d.getVar(var,exp)
  File "/space/bitbake-1.8.12/lib/bb/data_smart.py", line 167, in getVar
    return self.expand(value,var)
  File "/space/bitbake-1.8.12/lib/bb/data_smart.py", line 85, in expand
    s = __expand_python_regexp__.sub(python_sub, s)
  File "/space/bitbake-1.8.12/lib/bb/data_smart.py", line 71, in
python_sub
    s = eval(code)
  File "<string>", line 1, in <module>
  File "<bb>", line 6, in base_detect_branch
  File "<bb>", line 3, in base_get_metadata_git_branch
  File "<bb>", line 4, in base_get_scmbasepath
IndexError: list index out of range
ddhagood at sage:..OpenEmbedded/build> 

Other than the base directory I am using, this is straight out of the
Wiki.

This DID work with the Debian provided BitBake (to the extent that it
would at least TRY to build the files).



Notice: This e-mail is intended solely for use of the individual or entity to which it is addressed and may contain information that is proprietary, privileged, company confidential and/or exempt from disclosure under applicable law. If the reader is not the intended recipient or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited.  If this communication has been transmitted from a U.S. location it may also contain data subject to the International Traffic in Arms Regulations or U.S. Export Administration Regulations and cannot be disseminated, distributed or copied to foreign nationals, residing in the U.S. or abroad, without the prior approval of the U.S. Department of State or appropriate export licensing authority. If you have received this communication in error, please notify the sender by reply e-mail or collect telephone call and del
 ete or destroy all copies of this e-mail message, any physical copies made of this e-mail message and/or any file attachment(s).