Bug 10217

Preconditions/Environment
-------------------------
Installed the latest Yocto project build system release YPCore-Krogoth 2.1.1 “poky-krogoth-15.0.1.tar.bz2” on the development host (Ubuntu 14.04.4 LTS, Trusty Tahr)

$ mkdir /yocto-project
$ cd /yocto-project
$ tar –xjvf poky-krogoth-15.0.1.tar.bz2
$ mv poky-krogoth-15.0.1 poky

Obtained the access permission to the Apollo Lake-I Github repositories and cloned the “bsp-apollolake-i” repository into a local directory /yocto-project/ on the development host. 

$ cd /yocto-project/
$ git clone https://github.com/01org/bsp-apollolake-i -b beta


Triggering Action/Cause
-----------------------
Following the instructions in section 2.2.2 Your Fist Build of the BSP release notes “Apollo_LakeI_BSP_for_Yocto_Project_Release_Notes_Beta.pdf”.

If this is your first build, run the “setup.sh” script from your bsp-apollolake-i/ directory

$ cd bsp-apollolake-i/
$ ./setup.sh

Select an option:
1. Build kernel image with CAVS HD Audio driver (Default)
2. Build kernel image with CAVS SSP Audio driver
3. Build kernel image with legacy HD Audio driver
Default option is build kernel image with CAVS HD Audio driver. If no input is received within 20 secs, default will be used.
1

Select an option:
1. core-image-sato-sdk (Default)
2. core-image-sato
3. linux-kernel
4. custom
Default build target is core-image-sato-sdk. If no input is received within 20 secs, default target will be built.
1

--2016-09-04 16:13:35--  http://git.yoctoproject.org/cgit/cgit.cgi/meta-jarvis/tree/meta-jarvis/jarvis.bb
Resolving git.yoctoproject.org (git.yoctoproject.org)... 140.211.169.56
Connecting to git.yoctoproject.org (git.yoctoproject.org)|140.211.169.56|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘jarvis.bb’

    [ <=>                                                     ] 3,410       --.-K/s   in 0s

2016-09-04 16:13:36 (261 MB/s) - ‘jarvis.bb’ saved [3410]

SUCCESS: wget test is healthy.
Build directory yocto_build already exists
Proceed to update ingredients ...
rm: cannot remove ‘unsetup.sh’: No such file or directory
Building BSP with core-image-sato-sdk image ...
Fetching in Apollo Lake BSP ingredient now
[16:13:48] cloning git://git.openembedded.org/meta-openembedded to repo-ext/meta-openembedded
Cloning into 'repo-ext/meta-openembedded'...
Traceback (most recent call last):
  File "setup/combo-layer", line 597, in <module>
    ret = main()
  File "setup/combo-layer", line 593, in main
    actions.get(args[1], action_error)(confdata, args[1:])
  File "setup/combo-layer", line 178, in action_init
    subprocess.check_call("git clone -b %s %s %s" % (branch, conf.repos[name]['src_uri'], ldir), shell=True)
  File "/usr/lib/python2.7/subprocess.py", line 540, in check_call
    raise CalledProcessError(retcode, cmd)
CalledProcessError: Command 'git clone -b jethro git://git.openembedded.org/meta-openembedded repo-ext/meta-openembedded' returned non-zero exit status 141
Initial Repo Population: Apollo Lake BSP for linux-yocto ver-4.1

Combo-layer configuration:
[poky]
src_uri = git://git.yoctoproject.org/poky
local_repo_dir = repo-ext/poky
dest_dir = .
branch = jethro
last_revision = 40376446904ae3529be41737fed9a0b650ed167d
file_filter = bitbake documentation LICENSE meta meta-yocto meta-yocto-bsp oe-init-build-env scripts

[meta-openembedded]
src_uri = git://git.openembedded.org/meta-openembedded
local_repo_dir = repo-ext/meta-openembedded
dest_dir = meta-openembedded
branch = jethro
last_revision = cb7e68f2a39fa6f24add48fc7b8d38fb7291bb44
file_filter = meta-oe meta-gnome meta-python meta-xfce meta-filesystems meta-multimedia meta-networking

[meta-qt5]
src_uri = https://github.com/meta-qt5/meta-qt5
local_repo_dir = repo-ext/meta-qt5
dest_dir = meta-qt5
branch = jethro
last_revision = ea37a0bc987aa9484937ad68f762b4657c198617

[meta-measured]
src_uri = https://github.com/flihp/meta-measured.git
local_repo_dir = repo-ext/meta-measured
dest_dir = meta-measured
branch = master
last_revision = 66aca6bc94e35f3c5896455d2feed2a35f428d28

[meta-intel-iot-middleware]
src_uri = git://git.yoctoproject.org/meta-intel-iot-middleware
local_repo_dir = repo-ext/meta-intel-iot-middleware
dest_dir = meta-intel-iot-middleware
branch = master
last_revision = 821cf14c8304669d9ce0c5b87b9be5a6eecff6e5
file_filter = COPYING.MIT MAINTAINERS README conf recipes-devtools/mraa recipes-devtools/swig recipes-devtools/upm
fatal: Not a git repository (or any parent up to mount point /yocto-projects)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Patching BSP meta layer ...
fatal: Not a git repository (or any parent up to mount point /yocto-projects)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
fatal: Not a git repository (or any parent up to mount point /yocto-projects)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
=========================================================================
By default, this setup script will create a brand new repo which combines
meta-intel BSP layer and Yocto Project poky distro.
If you don't need git tracking, please 'rm -rf .git' now
=========================================================================
./build.sh: line 70: oe-init-build-env: No such file or directory

local.conf: machine: CAVS HD-Audio -- intel-corei7-64-cavs-hda

./build.sh: line 90: bitbake: command not found
Entering build status checker ...
./setup.sh: line 319: cd: ../yocto_build/build/tmp/deploy/images/intel-corei7-64-cavs-hda/: No such file or directory
BSP Build: FAILED!!!
HDDIMG was not generated!
Please check the build log for detailed failure.
$

Expectation
-----------

The instructions in the BSP release notes “Apollo_LakeI_BSP_for_Yocto_Project_Release_Notes_Beta.pdf” should be able to guide a user to successfully build a Yocto BSP image and perform all the tasks as described in the BSP release notes.

Actual Results
---------------
The build process failed with error messages and the Yocto BSP image is not created.

Reproducibility
---------------
5/5