From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/4] eglibc 2.14 upgrade
Date: Thu, 23 Jun 2011 09:26:31 -0700 [thread overview]
Message-ID: <4E036937.4040002@mentor.com> (raw)
In-Reply-To: <BANLkTimxc0yvPrtTu2NP69Pb_ByAzf_Wxg@mail.gmail.com>
On 06/22/2011 09:13 PM, Khem Raj wrote:
> On Wed, Jun 22, 2011 at 4:29 PM, Tom Rini <tom_rini@mentor.com> wrote:
>> On 06/22/2011 04:22 PM, Khem Raj wrote:
>>> On Wed, Jun 22, 2011 at 3:59 PM, Richard Purdie
>>> <richard.purdie@linuxfoundation.org> wrote:
>>>> On Wed, 2011-06-22 at 15:31 -0700, Khem Raj wrote:
>>>>> On Wed, Jun 22, 2011 at 1:28 PM, Mark Hatle <mark.hatle@windriver.com> wrote:
>>>>>> On 6/22/11 1:35 PM, Mark Hatle wrote:
>>>>>>> Since applying this update, I'm not longer getting an rpc/rpc.h file, which
>>>>>>> breaks various things like busybox mount.
>>>>>>>
>>>>>>> Is anyone else seeing this behavior?
>>>>>>
>>>>>> Reverting:
>>>>>>
>>>>>> 2a68cf4d315cdd18766de0c75928ff17846a6cd7 and
>>>>>> 190a946e9a4213944e3ee675c4b3e18701698e87
>>>>>>
>>>>>> fixed the problem for me. So there is definitely a problems in the upgrade.
>>>>>>
>>>>>
>>>>> onward looking rpc is now maintained with libtirpc starting glibc 2.14 rpc is
>>>>> not to be used from bundled code in glibc. If we dont have recipes for libtirpc
>>>>> then I will add that.
>>>>
>>>> There looks to be more than this wrong with this update. A quick
>>>> comparison shows the following changes in the list of files being
>>>> installed from do_install:
>>>>
>>>> -./lib/libmemusage.so
>>>> -./lib/libnss_hesiod-2.13.so
>>>> -./lib/libnss_nisplus-2.13.so
>>>> -./lib/libutil-2.13.so
>>>> -./lib/libresolv-2.13.so
>>>> -./lib/libm-2.13.so
>>>> -./lib/libnsl-2.13.so
>>>> -./lib/libnss_compat-2.13.so
>>>> -./lib/libnss_nis-2.13.so
>>>> -./lib/libnss_dns-2.13.so
>>>> -./lib/libanl-2.13.so
>>>> -./lib/libBrokenLocale-2.13.so
>>>> -./lib/libcrypt-2.13.so
>>>> -./etc/rpc
>>>> -./usr/lib/libnss_compat_pic.a
>>>> -./usr/lib/libnss_dns_pic.a
>>>> -./usr/lib/libnss_nisplus_pic.a
>>>> +./usr/lib/audit/sotruss-lib.so
>>>> -./usr/lib/libutil_pic.map
>>>> -./usr/lib/libBrokenLocale_pic.a
>>>> -./usr/lib/libBrokenLocale.a
>>>> -./usr/lib/libBrokenLocale_pic.map
>>>> -./usr/lib/libm.a
>>>> -./usr/lib/libnss_dns_pic.map
>>>> -./usr/lib/libm_pic.map
>>>> -./usr/lib/libnss_hesiod_pic.map
>>>> -./usr/lib/librpcsvc.a
>>>> -./usr/lib/libutil.a
>>>> -./usr/lib/libnss_compat_pic.map
>>>> -./usr/lib/libcrypt.a
>>>> -./usr/lib/libutil_pic.a
>>>> -./usr/lib/libanl.a
>>>> -./usr/lib/libnsl_pic.a
>>>> -./usr/lib/libresolv.a
>>>> -./usr/lib/libnss_hesiod_pic.a
>>>> -./usr/lib/libm_pic.a
>>>> -./usr/lib/libnsl_pic.map
>>>> -./usr/lib/libnss_nis_pic.map
>>>> -./usr/lib/libanl_pic.a
>>>> -./usr/lib/libcrypt_pic.map
>>>> -./usr/lib/libcrypt_pic.a
>>>> -./usr/lib/libnss_nis_pic.a
>>>> -./usr/lib/libresolv_pic.map
>>>> -./usr/lib/libresolv_pic.a
>>>> -./usr/lib/libanl_pic.map
>>>> -./usr/lib/libnss_nisplus_pic.map
>>>> -./usr/lib/libnsl.a
>>>> -./usr/bin/rpcgen
>>>> -./usr/bin/gencat
>>>> +./usr/bin/sotruss
>>>> -./usr/bin/localedef
>>>> -./usr/bin/locale
>>>> -./usr/sbin/rpcinfo
>>>> -./usr/sbin/nscd
>>>>
>>>> Some of these are rpc related but there are other issues too.
>>>>
>>>> I've reverted the upgrade itself for now until we have something in
>>>> place to address the issues and its actually had some testing...
>>>>
>>>
>>> some of these are due to rpc and others are due to nss being removed
>>> I need to backport the nss db re-implementation then most of it should
>>> be resolved
>>> I guess I will post 2.14 as additional recipes rather than replacement for 2.13
>>> that way we will get some soak time.
>>
>> Neither of those would explain the locale problem Otavio and I have seen:
>
> $ find ../../eglibc-2.14-r0+svnr14285/packages-split/ -name "*wae*"
> ../../eglibc-2.14-r0+svnr14285/packages-split/locale-base-wae-ch
> ../../eglibc-2.14-r0+svnr14285/packages-split/eglibc-localedata-wae-ch
> ../../eglibc-2.14-r0+svnr14285/packages-split/eglibc-localedata-wae-ch/usr/share/i18n/locales/wae_CH
>
> so don't know whats the problem you are having.
Well, in my case it's a brand new checkout of oe-core + meta-oe in
'distro-less' mode. Otavio saw the same thing with his custom distro
which just uses the default bits for libc features.
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-06-23 16:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 1:43 [PATCH 0/4] eglibc 2.14 upgrade Khem Raj
2011-06-22 1:43 ` [PATCH 1/4] eglibc: Upgrade recipes from 2.13 -> 2.14 Khem Raj
2011-06-22 1:43 ` [PATCH 2/4] eglibc-package.inc: Package newly added sotruss and supporting libraries Khem Raj
2011-06-22 1:43 ` [PATCH 3/4] binutils_2.21.bb: Fix ld segfault exposed by eglibc 2.14 on x86_64 Khem Raj
2011-06-22 1:43 ` [PATCH 4/4] tcmode-default.inc: Bump EGLIBCVERSION to 2.14 Khem Raj
2011-06-22 15:57 ` [PATCH 0/4] eglibc 2.14 upgrade Richard Purdie
2011-06-22 18:35 ` Mark Hatle
2011-06-22 20:28 ` Mark Hatle
2011-06-22 21:26 ` Tom Rini
2011-06-22 22:31 ` Khem Raj
2011-06-22 22:51 ` Mark Hatle
2011-06-22 22:59 ` Richard Purdie
2011-06-22 23:22 ` Khem Raj
2011-06-22 23:29 ` Tom Rini
2011-06-23 4:13 ` Khem Raj
2011-06-23 16:26 ` Tom Rini [this message]
2011-06-23 18:01 ` Khem Raj
2011-06-23 5:47 ` Martin Jansa
2011-06-23 6:07 ` Khem Raj
2011-06-23 8:43 ` Khem Raj
2011-06-23 13:31 ` Richard Purdie
2011-06-23 18:00 ` Khem Raj
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=4E036937.4040002@mentor.com \
--to=tom_rini@mentor.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