This sounds very odd. Can you give an example of this happening?
Ross
On 13 March 2018 at 03:08, Jason Wessel <jason.wes...@windriver.com> wrote:
> There are a number of other recipes outside oe-core that depend on
> alsa-lib and the rpm4 dependencies resolve sometimes to include
> alsa-lib and the packages in the other layers fail to install because
> the dependency cannot be resolved, despite the fact that libasound is
> installed.
>
> The simple is to add an RPROVIDES for alsa-lib to libasound which
> provides all the shared objects for alsa.
>
> Signed-off-by: Jason Wessel <jason.wes...@windriver.com>
> ---
> meta/recipes-multimedia/alsa/alsa-lib_1.1.5.bb | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/recipes-multimedia/alsa/alsa-lib_1.1.5.bb
> b/meta/recipes-multimedia/alsa/alsa-lib_1.1.5.bb
> index c5bf107..f7f01e8 100644
> --- a/meta/recipes-multimedia/alsa/alsa-lib_1.1.5.bb
> +++ b/meta/recipes-multimedia/alsa/alsa-lib_1.1.5.bb
> @@ -25,6 +25,7 @@ FILES_alsa-server = "${bindir}/*"
> FILES_alsa-conf = "${datadir}/alsa/"
>
> RDEPENDS_libasound = "alsa-conf"
> +RPROVIDES_libasound = "alsa-lib"
>
> # alsa-lib gets automatically added to alsa-lib-dev dependencies, but the
> # alsa-lib package doesn't exist. libasound is the real library package.
> --
> 2.7.4
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
