Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Raspberry Pi3 agl-demo build failure on directory mismatch

Description

After issuing "bitbake agl-demo-platform" for a Raspberry Pi 3 build on Raspbian 8, I receive the following:

ERROR: Unable to parse /home/pi/dev/agl/meta-raspberry/conf/layer.conf: [Errno 2] file /home/pi/dev/agl/meta-raspberry/conf/layer.conf not found

The error is accurate as meta-raspberry doesn't exist. However, a directory named meta-raspberrypi does exist. This appears to be a simple name mismatch populated in build/conf/bblayers.conf:

BBLAYERS =+ "${METADIR}/meta-raspberry"

...as sourced from the Raspberry Pi 2 & 3 templates:

$ grep meta-raspberry meta-agl/templates/machine/raspberrypi2/50_bblayers.conf.inc BBLAYERS =+ "${METADIR}/meta-raspberry" $ grep meta-raspberry meta-agl/templates/machine/raspberrypi3/50_bblayers.conf.inc BBLAYERS =+ "${METADIR}/meta-raspberry"

For reference, here's the history of my build arguments:

cd ~/dev/agl repo init -b blowfish -u https://gerrit.automotivelinux.org/gerrit/AGL/AGL-repo repo sync source meta-agl/scripts/aglsetup.sh -m raspberrypi3 agl-demo agl-appfw-smack bitbake agl-demo-platform

See the attached log for console output. Issue aside, this log might be useful for seeing what's generally happening on someone else's system up to the point of the error.

Environment

Raspberry Pi 3, Raspbian 8

Attachments

1

Activity

Show:

Jan-Simon Moeller 
October 13, 2016 at 8:07 AM

As Leon said, use:

mkdir ~/dev/agl-master
cd ~/dev/agl-master
repo init -u https://gerrit.automotivelinux.org/gerrit/AGL/AGL-repo
repo sync
source meta-agl/scripts/aglsetup.sh -m raspberrypi3 agl-demo agl-appfw-smack agl-devel
bitbake agl-demo-platform

Leon Anavi 
October 12, 2016 at 10:08 PM

Hi,

Jan-Simon has fixed this issue in the master branch on 26 September. Please use the master branch of AGL for building images for Raspberry Pi 2 or 3.

Best regards, Leon

Fixed

Details

Assignee

Reporter

Priority

Created October 12, 2016 at 8:21 PM
Updated January 8, 2017 at 8:16 PM
Resolved October 12, 2016 at 10:08 PM

Flag notifications