[OE-core] daisy: runtime-reverse/udev-hwdb missing during do_rootfs

[Darren Hart]

Hi all,

I've hit the following on a custom image recipe (based on core-image):

| Configuring run-postinsts.
|
| NOTE: Installing complementary packages ...
| NOTE: Running intercept scripts:
| NOTE: Executing write_package_manifest ...
| DEBUG: Executing python function write_package_manifest
| DEBUG: Python function write_package_manifest finished
| NOTE: Executing license_create_manifest ...
| DEBUG: Executing shell function license_create_manifest
| ls: cannot access
/build/yocto/daisy/intel-corei7-64_20140718205500/build/tmp/sysroots/intel-
internal-corei7-64/pkgdata/runtime-reverse/udev-hwdb: No such file or
directory
| readlink: missing operand
| Try 'readlink --help' for more information.
| basename: missing operand
| Try 'basename --help' for more information.
| WARNING: exit code 1 from a shell command.
| DEBUG: Python function do_rootfs finished
| ERROR: Function failed: license_create_manifest (log file is located at
/build/yocto/daisy/intel-corei7-64_20140718205500/build/tmp/work/intel_inte
rnal_corei7_64-eywa-linux/core-image-minimal-initramfs/1.0-r0/temp/log.do_r
ootfs.15414)
ERROR: Task 150 
(/build/yocto/daisy/intel-corei7-64_20140718205500/poky/meta/recipes-core/i
mages/core-image-minimal-initramfs.bb, do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 4727 tasks of which 4697 didn't need to be
rerun and 1 failed.
Waiting for 0 running tasks to finish:




Using the daisy branch of the following layers (poky, meta-intel, and
meta-oe layers):

BBLAYERS ?= " \
  /build/yocto/daisy/intel-corei7-64_20140718205500/poky/meta \
  /build/yocto/daisy/intel-corei7-64_20140718205500/poky/meta-yocto \
  /build/yocto/daisy/intel-corei7-64_20140718205500/poky/meta-yocto-bsp \
  "
BBLAYERS_NON_REMOVABLE ?= " \
  /build/yocto/daisy/intel-corei7-64_20140718205500/poky/meta \
  /build/yocto/daisy/intel-corei7-64_20140718205500/poky/meta-yocto \
  "

# Automatically generated by bitbake-shell (bs)
BBLAYERS += 
"/build/yocto/daisy/intel-corei7-64_20140718205500/poky/meta-yocto"
BBLAYERS += 
"/build/yocto/daisy/intel-corei7-64_20140718205500/meta-openembedded/meta-n
etworking"
BBLAYERS += "/build/yocto/daisy/intel-corei7-64_20140718205500/meta-intel"
BBLAYERS += 
"/build/yocto/daisy/intel-corei7-64_20140718205500/meta-openembedded/meta-x
fce"
BBLAYERS += 
"/build/yocto/daisy/intel-corei7-64_20140718205500/meta-openembedded/meta-o
e"
BBLAYERS += 
"/build/yocto/daisy/intel-corei7-64_20140718205500/meta-openembedded/meta-m
ultimedia"
BBLAYERS += 
"/build/yocto/daisy/intel-corei7-64_20140718205500/meta-openembedded/meta-g
nome"
BBLAYERS += "/build/yocto/daisy/intel-corei7-64_20140718205500/eywa/meta"
BBLAYERS += 
"/build/yocto/daisy/intel-corei7-64_20140718205500/eywa/meta-intel-internal
"
BBLAYERS += "/build/yocto/daisy/intel-corei7-64_20140718205500/poky/meta"


Is this a known issue? Have others hit this or have a workaround?


-- 
Darren Hart					Open Source Technology Center
darren.hart at intel.com				            Intel Corporation