Wind River Support Network

Description

libvirt checks for features during configuration. if we do a platform build which happens to have cyrus-sasl in sysroot, populates the sstate-cache, and then reuse sstate-cache for another platform build which happens to not have cyrus-sasl in sysroot, libvirt fails to install because of missing cyrus-sasl:

| Computing transaction...error: Can't install libvirt-1.1.2-r1@x86_64: 
no package provides cyrus-sasl >= 2.1.25

In order to be able to share libvirt in shared sstate-cache, we need explicit config that can then be discovered via package signature in sstate.

Workaround

Fix is this simple recipe:

eperhal@shelob:/home2/eperhal/src/wrl-ecs/layers/meta-wrl-ecs/recipes-extended/libvirt$
more libvirt_1.1.2.bbappend

PRINC := "${@int(PRINC) + 1}"

PACKAGECONFIG[sasl] = "--with-sasl,--without-sasl,cyrus-sasl,cyrus-sasl"
eperhal@shelob:/home2/eperhal/src/wrl-ecs/layers/meta-wrl-ecs/recipes-extended/libvirt$ 


But should really be in product instead.

Steps to Reproduce

Build libvirt, configured with cyrus-sasl, to a state.

Start a new project against the sstate, with libvirt, but without cyrus-sasl.
Build.