From: "Khem Raj" <raj.khem@gmail.com>
To: kai <kai.kang@windriver.com>, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] libcgroup: remove static pam library
Date: Wed, 25 Aug 2021 08:35:41 -0700 [thread overview]
Message-ID: <d9124478-3ab8-26c8-75d5-e79cb3f17c9a@gmail.com> (raw)
In-Reply-To: <20210825081054.40523-1-kai.kang@windriver.com>
On 8/25/21 1:10 AM, kai wrote:
> From: Kai Kang <kai.kang@windriver.com>
>
> libpam disables static build by default, so remove static pam library of
> libcgroup. Otherwise it complains QA issue:
>
> | ERROR: libcgroup-2.0-r0 do_package: QA Issue: libcgroup:
> Files/directories were installed but not shipped in any package:
> | /lib/security/pam_cgroup.a
>
> Signed-off-by: Kai Kang <kai.kang@windriver.com>
> ---
> meta/recipes-core/libcgroup/libcgroup_2.0.bb | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/recipes-core/libcgroup/libcgroup_2.0.bb b/meta/recipes-core/libcgroup/libcgroup_2.0.bb
> index bc0a75d46c..f48b8ece9b 100644
> --- a/meta/recipes-core/libcgroup/libcgroup_2.0.bb
> +++ b/meta/recipes-core/libcgroup/libcgroup_2.0.bb
> @@ -31,4 +31,5 @@ FILES:${PN}-dev += "${base_libdir}/security/*.la"
> do_install:append() {
> # Until we ship the test suite, this library isn't useful
> rm -f ${D}${libdir}/libcgroupfortesting.*
> + rm -f ${D}${base_libdir}/security/pam_cgroup.a
> }
>
should this be simply packaged into FILES_${PN}-staticdev instead ?
>
>
>
>
next prev parent reply other threads:[~2021-08-25 15:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 8:10 [PATCH] libcgroup: remove static pam library kai
2021-08-25 15:35 ` Khem Raj [this message]
2021-08-26 1:43 ` [OE-core] " kai
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=d9124478-3ab8-26c8-75d5-e79cb3f17c9a@gmail.com \
--to=raj.khem@gmail.com \
--cc=kai.kang@windriver.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox