Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] eglibc: migrate configurability from oe
Date: Fri, 03 Jun 2011 10:51:27 +0100	[thread overview]
Message-ID: <1307094687.5715.2.camel@rex> (raw)
In-Reply-To: <EEAC1D96-7E8D-4496-9FA1-E41860CA131E@dominion.thruhere.net>

On Fri, 2011-06-03 at 10:57 +0200, Koen Kooi wrote:
> Op 3 jun 2011, om 10:22 heeft Richard Purdie het volgende geschreven:
> 
> > On Fri, 2011-06-03 at 14:47 +0800, Kang Kai wrote:
> >> From: Kang Kai <kai.kang@windriver.com>
> >> 
> >> Migrate configurability from oe, try to shrink minimal image size
> >> 
> >> The switch is in local.conf.sample, uncomment the line
> >> DISTRO_FEATURES_EGLIBC = ""
> >> and write what options you want to enable.
> >> 
> >> If want to disable locale-code charsets or locales, you have to uncomment
> >> PACKAGE_NO_GCONV = 1
> >> Because without this, it fails on package_do_split_gconvs in libc-package.bbclass
> > 
> > I have some comments:
> > 
> > a) I think these should become flags in DISTRO_FEATURES with an
> > "eglibc-" prefix so something like "spawn" would become "eglibc-spawn"
> 
> Taking a step back here, uclibc has the same configurability, so
> wouldn't it make sense to align both (where possible) and just have
> 'libc-spawn' in DISTRO_FEATURES?

If multiple libc's can support it, it would seem to make sense to have a
common option.

It would really mean a libc should complain loudly when it sees an
option it can't support though (e.g. glibc)...

Cheers,

Richard




  reply	other threads:[~2011-06-03  9:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-03  6:47 [PATCH 0/1] eglibc: enable eglibc configurability V2 Kang Kai
2011-06-03  6:47 ` [PATCH 1/1] eglibc: migrate configurability from oe Kang Kai
2011-06-03  8:22   ` Richard Purdie
2011-06-03  8:54     ` Kang Kai
2011-06-03  9:52       ` Richard Purdie
2011-06-03  8:57     ` Koen Kooi
2011-06-03  9:51       ` Richard Purdie [this message]
2011-06-03 18:00       ` Khem Raj
2011-06-03  9:49     ` Phil Blundell
2011-06-03 11:32 ` [PATCH 0/1] eglibc: enable eglibc configurability V2 Phil Blundell
2011-06-03 11:50   ` Richard Purdie
2011-06-03 12:06     ` Phil Blundell
  -- strict thread matches above, loose matches on Subject: below --
2011-06-03  1:41 [PATCH 0/1] eglibc: enable eglibc configurability Kang Kai
2011-06-03  1:41 ` [PATCH 1/1] eglibc: migrate configurability from oe Kang Kai
2011-06-03  1:14   ` Saul Wold
2011-06-03  1:23     ` Kang Kai

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=1307094687.5715.2.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