All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] libc-package bbclass: fix binary localedata dependency code
Date: Wed, 03 Aug 2011 08:26:05 +0100	[thread overview]
Message-ID: <1312356365.3223.23.camel@lenovo.internal.reciva.com> (raw)
In-Reply-To: <26D3BBA8-8A7F-4B0C-A235-8307DD46B3CE@dominion.thruhere.net>

On Wed, 2011-08-03 at 09:03 +0200, Koen Kooi wrote:
> If you look at e.g. http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/testlab/commit/?h=yocto&id=0fb50099
> 
> -locale_base_en_us -> eglibc_localedata_en_us;
> -locale_base_en_us -> localedef;
> -locale_base_en_us -> eglibc_charmap_utf_8;
> -localedef -> libc6;
> +locale_base_en_us -> eglibc_binary_localedata_en_us;
> 
> That shows that locale-base-foo drops some deps like the charmap when switching to binary locales. There's other breakage in that build clouding the diff, so I copied the relevant lines above.

I think that's expected.  IIRC, the charmap files are inputs to
localedef and the relevant bits from them are fully captured in the
binary archive output.  So, if you're using a pregenerated binary
locale, you don't need the charmap (or localedata, which is also a
source file) at run time.

p.





  reply	other threads:[~2011-08-03  7:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-02 14:47 [PATCH] libc-package bbclass: fix binary localedata dependency code Koen Kooi
2011-08-02 14:55 ` Koen Kooi
2011-08-02 15:01   ` Phil Blundell
2011-08-03  6:19     ` Koen Kooi
2011-08-03  6:39       ` Phil Blundell
2011-08-03  7:03         ` Koen Kooi
2011-08-03  7:26           ` Phil Blundell [this message]
2011-08-04 22:00       ` Phil Blundell
2011-08-04 22:38         ` Kamble, Nitin A
2011-08-17 15:51         ` Khem Raj
2011-08-10  6:14     ` Koen Kooi
2011-08-12  4:43       ` Kamble, Nitin A
2011-08-17 15:50         ` 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=1312356365.3223.23.camel@lenovo.internal.reciva.com \
    --to=philb@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.