Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] eglibc: migrate configurability from oe
Date: Tue, 07 Jun 2011 10:53:56 +0100	[thread overview]
Message-ID: <1307440436.2529.4745.camel@phil-desktop> (raw)
In-Reply-To: <46fc6e81f626e87f30a0d0980ed2b8fc3747e6be.1307438945.git.kai.kang@windriver.com>

On Tue, 2011-06-07 at 17:42 +0800, Kang Kai wrote:
> -DISTRO_FEATURES ?= "alsa bluetooth ext2 irda pcmcia usbgadget usbhost wifi nfs zeroconf pci"
> +DISTRO_FEATURES ?= "alsa bluetooth ext2 irda pcmcia usbgadget usbhost wifi nfs zeroconf pci \
> +		libc-ipv6 libc-backtrace libc-big-macros libc-bsd libc-cxx-tests libc-catgets libc-charsets libc-crypt \

I don't think it is a good idea to invent a new "libc-ipv6" feature; you
can just use the existing "ipv6" one.  This is probably true for some of
your others too.

> +        # try to fix disable charsets/locales/locale-code compile fail
> +        if 'libc-charsets' in distro_features and 'libc-locales' in distro_features and 'libc-locale-code' in distro_features:
> +            bb.data.setVar('PACKAGE_NO_GCONV', '0', d)
> +        else:
> +            bb.data.setVar('PACKAGE_NO_GCONV', '1', d)

Does that actually work?

p.




  parent reply	other threads:[~2011-06-07  9:57 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-07  9:42 [PATCH 0/2] eglibc: migrate configurability from oe V3 Kang Kai
2011-06-07  9:42 ` [PATCH 1/2] bitbake: add another local configuration file Kang Kai
2011-06-07 15:56   ` Saul Wold
2011-06-07  9:42 ` [PATCH 2/2] eglibc: migrate configurability from oe Kang Kai
2011-06-07  9:48   ` Koen Kooi
2011-06-08  1:45     ` Kang Kai
2011-06-08  6:25       ` Koen Kooi
2011-06-08  6:35         ` Kang Kai
2011-06-08  6:42           ` Martin Jansa
2011-06-07  9:53   ` Phil Blundell [this message]
2011-06-08  1:59     ` Kang Kai
2011-06-08  2:34       ` Khem Raj
2011-06-07 17:50   ` Khem Raj
2011-06-08  2:04     ` Kang Kai
  -- strict thread matches above, loose matches on Subject: below --
2011-06-08  5:56 [PATCH 0/2] eglibc: migrate configurability from oe V4 Kang Kai
2011-06-08  5:56 ` [PATCH 2/2] eglibc: migrate configurability from oe Kang Kai
2011-06-10  3:13   ` Khem Raj
2011-06-10  3:25     ` Kang Kai
2011-06-13  9:01 [PATCH 0/2] eglibc: migrate configurability from oe V5 Kang Kai
2011-06-13  9:01 ` [PATCH 2/2] eglibc: migrate configurability from oe Kang Kai
2011-06-13  9:05   ` Phil Blundell
2011-06-13  9:15     ` Kang Kai
2011-06-13  9:27       ` Phil Blundell
2011-06-13  9:34         ` Kang Kai
2011-06-13  9:42           ` Phil Blundell
2011-06-13 10:00             ` Martin Jansa
2011-06-13 11:07               ` 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=1307440436.2529.4745.camel@phil-desktop \
    --to=pb@pbcl.net \
    --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