From: Kang Kai <Kai.Kang@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] nss: avoid to use the hardcode kernel version
Date: Fri, 4 Apr 2014 10:53:05 +0800 [thread overview]
Message-ID: <533E1E91.1020405@windriver.com> (raw)
In-Reply-To: <1396526409.2910.86.camel@ted>
On 2014年04月03日 20:00, Richard Purdie wrote:
> On Wed, 2014-04-02 at 10:35 +0800, Kang Kai wrote:
>> On 2014年03月31日 22:20, Kai Kang wrote:
>>> From: Roy Li <rongqing.li@windriver.com>
>>>
>>> When native package is built, use the uname to return the kernel version.
>>>
>>> When target is built, read kernel version from ${STAGING_KERNEL_DIR}/kernel-abiversion
>>> to avoid to use the hardcode kernel version.
>>>
>>> Signed-off-by: Roy Li <rongqing.li@windriver.com>
>>> Signed-off-by: Kai Kang <kai.kang@windriver.com>
>>> ---
>>> meta/recipes-support/nss/nss.inc | 15 +++++++++++++--
>>> 1 file changed, 13 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/meta/recipes-support/nss/nss.inc b/meta/recipes-support/nss/nss.inc
>>> index 404decc..f24da68 100644
>>> --- a/meta/recipes-support/nss/nss.inc
>>> +++ b/meta/recipes-support/nss/nss.inc
>>> @@ -26,6 +26,7 @@ SRC_URI_append_class-target = "\
>>> inherit siteinfo
>>> PR = "r0"
>>> DEPENDS = "sqlite3 nspr zlib nss-native"
>>> +DEPENDS_append_class-target += "virtual/kernel"
>>> DEPENDS_class-native = "sqlite3-native nspr-native zlib-native"
>>> RDEPENDS_${PN} = "perl"
>>>
>>> @@ -37,12 +38,24 @@ TARGET_CC_ARCH += "${LDFLAGS}"
>>> do_compile_prepend_class-native() {
>>> export NSPR_INCLUDE_DIR=${STAGING_INCDIR_NATIVE}
>>> export NSPR_LIB_DIR=${STAGING_LIBDIR_NATIVE}
>>> + export OS_RELEASE=`uname -r`
>>> }
>>>
>>> do_compile_prepend_class-nativesdk() {
>>> export LDFLAGS=""
>>> }
>>>
>>> +do_compile_prepend_class-target() {
>>> + export OS_RELEASE=`cat ${STAGING_KERNEL_DIR}/kernel-abiversion|sed 's/-.*//'`
>>> +}
>>> +
>>> +do_install_prepend_class-native() {
>>> + export OS_RELEASE=`uname -r`
>>> +}
>>> +
>>> +do_install_prepend_class-target() {
>>> + export OS_RELEASE=`cat ${STAGING_KERNEL_DIR}/kernel-abiversion|sed 's/-.*//'`
>>> +}
>>> do_compile() {
>>> export CROSS_COMPILE=1
>>> export NATIVE_CC="gcc"
>>> @@ -57,7 +70,6 @@ do_compile() {
>>> export NSS_USE_SYSTEM_SQLITE=1
>>> export NSS_ENABLE_ECC=1
>>>
>>> - export OS_RELEASE=3.4
>> How about use var LINUXLIBCVERSION:
>>
>> export OS_RELEASE="${@d.getVar('LINUXLIBCVERSION', True)}"
>>
>> it should be the same value with kernel version, right?
> As others have replied, that is usually much more recent than the oldest
> kernel we support. What does nss do with this value? Is it about the
> header versions? Would something run on an older kernel with a newer
> value for OS_RELEASE?
I misunderstanding the usage of LINUXLIBCVERSION. What nss needs is just
current kernel version to export for build:
- export OS_RELEASE=3.4
Currently it is a fix string, and I think it is a problem.
Regards,
Kai
>
> We also have the OLDEST_KERNEL variable (currently at 2.6.16) FWIW.
>
> Cheers,
>
> Richard
>
>
>
--
Regards,
Neil | Kai Kang
next prev parent reply other threads:[~2014-04-04 2:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 14:20 [PATCH] nss: avoid to use the hardcode kernel version Kai Kang
2014-03-31 14:20 ` Kai Kang
2014-03-31 14:33 ` Otavio Salvador
2014-03-31 15:10 ` Martin Jansa
2014-03-31 16:32 ` Richard Purdie
2014-04-01 1:40 ` Kang Kai
2014-03-31 20:49 ` Otavio Salvador
2014-04-02 2:35 ` Kang Kai
2014-04-02 3:35 ` Khem Raj
2014-04-03 12:00 ` Richard Purdie
2014-04-03 13:13 ` Paul Eggleton
2014-04-03 13:49 ` Phil Blundell
2014-04-03 13:53 ` Paul Eggleton
2014-04-04 2:53 ` Kang Kai [this message]
2014-03-31 16:30 ` Richard Purdie
-- strict thread matches above, loose matches on Subject: below --
2014-02-13 3:48 rongqing.li
2014-02-13 11:45 ` David Nyström
2014-02-13 12:04 ` Richard Purdie
2014-02-13 3:34 rongqing.li
2014-02-13 5:04 ` Rongqing Li
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=533E1E91.1020405@windriver.com \
--to=kai.kang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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