From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: eglibc issuettes continued
Date: Fri, 08 Jul 2011 17:49:10 +0100 [thread overview]
Message-ID: <1310143750.20015.911.camel@rex> (raw)
In-Reply-To: <1310139697.6337.134.camel@phil-desktop>
On Fri, 2011-07-08 at 16:41 +0100, Phil Blundell wrote:
> I'm not sure whether there are pending patches which will address these
> or not, but with a fresh pull from today I'm still not getting very good
> packaging for eglibc 2.13. Specifically:
>
> WARNING: For recipe eglibc, the following files were installed but not
> shipped in any package:
> WARNING: /etc/localtime
> WARNING: /etc/rpc
> WARNING: /etc/ld.so.conf
> WARNING: /lib/gconv/ISO-2022-CN-EXT.so
> WARNING: /lib/gconv/IBM921.so
> [... etc ...]
> WARNING: /lib/gconv/.debug/ISO-2022-CN-EXT.so
> WARNING: /lib/gconv/.debug/IBM921.so
> [... etc ...]
> WARNING: /share/i18n/charmaps/ISO-8859-15.gz
> WARNING: /share/i18n/charmaps/IBM285.gz
> [... etc ...]
> WARNING: /share/i18n/locales/ss_ZA
> WARNING: /share/i18n/locales/is_IS
> [... etc ...]
> WARNING: QA Issue: libc-extra-nss rdepends on eglibc-dev
> WARNING: QA Issue: libc-thread-db rdepends on eglibc-dev
> ERROR: QA run found fatal errors. Please consider fixing them.
>
> I'm not sure if these are actually new or not, though. It's possible
> that they've been there for ages and I only just noticed.
I'm guessing something is going wrong with prefixes somewhere. I'm
certainly not seeing the bulk of those locally...
Cheers,
Richard
next prev parent reply other threads:[~2011-07-08 16:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 15:41 eglibc issuettes continued Phil Blundell
2011-07-08 16:49 ` Richard Purdie [this message]
2011-07-08 16:53 ` Phil Blundell
2011-07-08 16:59 ` Kamble, Nitin A
2011-07-08 17:19 ` Richard Purdie
2011-07-08 17:22 ` Kamble, Nitin A
2011-07-08 17:24 ` Richard Purdie
2011-07-08 20:53 ` Koen Kooi
2011-07-08 20:23 ` Phil Blundell
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=1310143750.20015.911.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--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