From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: Mark Asselstine <mark.asselstine@windriver.com>
Cc: meta-virtualization@yoctoproject.org
Subject: Re: [PATCH] libvirt: fixup multiple shlib providers
Date: Wed, 2 Oct 2019 14:13:02 -0400 [thread overview]
Message-ID: <20191002181259.GA54356@gmail.com> (raw)
In-Reply-To: <20190930154558.31698-1-mark.asselstine@windriver.com>
merged.
Bruce
In message: [meta-virtualization] [PATCH] libvirt: fixup multiple shlib providers
on 30/09/2019 Mark Asselstine wrote:
> Build libvirt results in the follow warning:
> ERROR: libvirt-5.5.0-r0 do_package: libvirt-ptest: Multiple shlib providers for libvirt-admin.so.0: libvirt, libvirt-ptest
> (used by files: ./tmp/work/aarch64-overc-linux/libvirt/5.5.0-r0/packages-split/libvirt-ptest/usr/lib/libvirt/ptest/tools/virt-admin)
> ERROR: libvirt-5.5.0-r0 do_package: libvirt: Multiple shlib providers for libvirt-admin.so.0: libvirt, libvirt-ptest
> (used by files: ./tmp/work/aarch64-overc-linux/libvirt/5.5.0-r0/packages-split/libvirt/usr/bin/virt-admin)
>
> This is caused by the introduction of a shlib provider check added to
> openembedded-core (commit 61c413690034 [package: Multiple
> shlib_providers for the same file should error]). You can see the
> issue and solution discussed more here
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=4628
>
> Since the ptest version of the shared library will only be used by the
> ptest package so we can use PRIVATE_LIBS to have the shlib providers
> list.
>
> Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
> ---
> recipes-extended/libvirt/libvirt_5.5.0.bb | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/recipes-extended/libvirt/libvirt_5.5.0.bb b/recipes-extended/libvirt/libvirt_5.5.0.bb
> index de936c4..53f4b3e 100644
> --- a/recipes-extended/libvirt/libvirt_5.5.0.bb
> +++ b/recipes-extended/libvirt/libvirt_5.5.0.bb
> @@ -357,6 +357,8 @@ EXTRA_OECONF += " \
>
> EXTRA_OEMAKE = "BUILD_DIR=${B} DEST_DIR=${D}${PTEST_PATH} PTEST_DIR=${PTEST_PATH} SYSTEMD_UNIT_DIR=${systemd_system_unitdir}"
>
> +PRIVATE_LIBS_${PN}-ptest_append = "libvirt-admin.so.0"
> +
> do_compile_ptest() {
> oe_runmake -C tests buildtest-TESTS
> }
> --
> 2.21.0
>
> --
> _______________________________________________
> meta-virtualization mailing list
> meta-virtualization@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-virtualization
prev parent reply other threads:[~2019-10-02 18:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 15:45 [PATCH] libvirt: fixup multiple shlib providers Mark Asselstine
2019-10-02 18:13 ` Bruce Ashfield [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191002181259.GA54356@gmail.com \
--to=bruce.ashfield@gmail.com \
--cc=mark.asselstine@windriver.com \
--cc=meta-virtualization@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.