From: Pascal Ouyang <xin.ouyang@windriver.com>
To: lei yang <yanglei.fage@gmail.com>
Cc: openembedded-core@www.linuxtogo.org,
openembedded-core@lists.openembedded.org
Subject: Re: [V2 PATCH] libcgroup: fix the QA issue for pam_cgroup.so*
Date: Mon, 28 Jan 2013 09:43:29 +0800 [thread overview]
Message-ID: <5105D7C1.6040700@windriver.com> (raw)
In-Reply-To: <CAHsH0E-tkhtD-30XWaLr8AbC-Xn=gi9+aYqWsnoQ06ywVd-isQ@mail.gmail.com>
于 2013年01月26日 18:33, lei yang 写道:
> On Sat, Jan 26, 2013 at 5:13 PM, Pascal Ouyang <xin.ouyang@windriver.com> wrote:
>> 于 2013年01月24日 19:25, Xin Ouyang 写道:
>>
>>> PAM modules in ${base_libdir}/security/ should be binary .so files,
>>> not symlinks, so fix this. Since pam_cgroup.so is installed into
>>> ${base_libdir}/security, move libcgroup.so.* to ${base_libdir} to
>>> avoid "unsafe-references-in-binaries" QA issue.
>>>
>>> Signed-off-by: Xin Ouyang <Xin.Ouyang@windriver.com>
>>> ---
>>> meta/recipes-core/libcgroup/libcgroup_0.37.1.bb | 15 +++++++++++++--
>>> 1 file changed, 13 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/meta/recipes-core/libcgroup/libcgroup_0.37.1.bb
>>> b/meta/recipes-core/libcgroup/libcgroup_0.37.1.bb
>>> index e74f831..d217f7b 100644
>>> --- a/meta/recipes-core/libcgroup/libcgroup_0.37.1.bb
>>> +++ b/meta/recipes-core/libcgroup/libcgroup_0.37.1.bb
>>> @@ -23,5 +23,16 @@ FILES_cgroups-pam-plugin =
>>> "${base_libdir}/security/pam_cgroup.so*"
>>> FILES_${PN}-dbg += "${base_libdir}/security/.debug"
>>> FILES_${PN}-dev += "${base_libdir}/security/*.la"
>>>
>>> -# We really need the symlink so :(
>>> -INSANE_SKIP_cgroups-pam-plugin = "dev-so"
>>> +do_install_append() {
>>> + # Moving libcgroup to base_libdir
>>> + if [ ! ${D}${libdir} -ef ${D}${base_libdir} ]; then
>>> + mkdir -p ${D}/${base_libdir}/
>>> + mv -f ${D}${libdir}/libcgroup.so.* ${D}${base_libdir}/
>>> + ln -sf ${D}${base_libdir}/libcgroup.so.1
>>> ${D}${libdir}/libcgroup.so
>>
>>
>> I should not use absolute path for this symlink here.
>>
>> rel_lib_prefix=`echo ${libdir} | sed 's,\(^/\|\)[^/][^/]*,..,g'`
>> ln -sf ${rel_lib_prefix}${base_libdir}/libcgroup.so.1 \
>>
>
> I think use
>
> cd ${D}
> ln -sf libcgroup.so.1 ${D}${libdir}/libcgroup.so
>
> should be OK, no need sed to handle
libcgroup.so.1 is now moved to ${base_libdir}, so just sed. :)
- Pascal
>
>
> Lei
>
>> ${D}${libdir}/libcgroup.so
>>
>> V3 will be sent. Thanks.
>>
>> - Pascal
>>
>>
>>> + fi
>>> + # pam modules in ${base_libdir}/security/ should be binary .so
>>> files, not symlinks.
>>> + if [ -f ${D}${base_libdir}/security/pam_cgroup.so.0.0.0 ]; then
>>> + mv -f ${D}${base_libdir}/security/pam_cgroup.so.0.0.0
>>> ${D}${base_libdir}/security/pam_cgroup.so
>>> + rm -f ${D}${base_libdir}/security/pam_cgroup.so.*
>>> + fi
>>> +}
>>>
>>
>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
--
- Pascal
prev parent reply other threads:[~2013-01-28 1:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 11:25 [V2 PATCH] libcgroup: fix the QA issue for pam_cgroup.so* Xin Ouyang
2013-01-24 11:32 ` Burton, Ross
2013-01-26 9:13 ` Pascal Ouyang
2013-01-26 10:33 ` lei yang
2013-01-28 1:43 ` Pascal Ouyang [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=5105D7C1.6040700@windriver.com \
--to=xin.ouyang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-core@www.linuxtogo.org \
--cc=yanglei.fage@gmail.com \
/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