From: Kang Kai <Kai.Kang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] eglibc: migrate configurability from oe
Date: Mon, 13 Jun 2011 17:15:00 +0800 [thread overview]
Message-ID: <4DF5D514.3030102@windriver.com> (raw)
In-Reply-To: <1307955932.6879.12.camel@lenovo.internal.reciva.com>
On 2011年06月13日 17:05, Phil Blundell wrote:
> On Mon, 2011-06-13 at 17:01 +0800, Kang Kai wrote:
>> -DISTRO_FEATURES ?= "alsa bluetooth ext2 irda pcmcia usbgadget usbhost wifi nfs zeroconf pci"
>> +DISTRO_FEATURES_LIBC ?= "ipv6 libc-backtrace libc-big-macros libc-bsd libc-cxx-tests libc-catgets libc-charsets libc-crypt \
>> + libc-crypt-ufc libc-db-aliases libc-envz libc-fcvt libc-fmtmsg libc-fstab libc-ftraverse \
>> + libc-getlogin libc-idn libc-inet libc-inet-anl libc-libm libc-libm-big libc-locales libc-locale-code \
>> + libc-memusage libc-nis libc-nsswitch libc-rcmd libc-rtld-debug libc-spawn libc-streams libc-sunrpc \
>> + libc-utmp libc-utmpx libc-wordexp libc-posix-clang-wchar libc-posix-regexp libc-posix-regexp-glibc \
>> + libc-posix-wchar-io"
>> +
>> +DISTRO_FEATURES ?= "alsa bluetooth ext2 irda pcmcia usbgadget usbhost wifi nfs zeroconf pci ${DISTRO_FEATURES_LIBC}"
> Why is ipv6 in DISTRO_FEATURES_LIBC rather than DISTRO_FEATURES?
Because eglibc has a feature libc-ipv6, and DISTRO_FEATURES has a ipv6
already. It is not needed to import a new feature name on the same
things, so use original ipv6. And eglibc still needs provide this
option, then put it in DISTRO_FEATURES_LIBC.
> p.
>
Regards,
Kai
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2011-06-13 9:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 9:01 [PATCH 0/2] eglibc: migrate configurability from oe V5 Kang Kai
2011-06-13 9:01 ` [PATCH 1/2] bitbake: add local.conf.sample.extended 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 [this message]
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
-- 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-07 9:42 [PATCH 0/2] eglibc: migrate configurability from oe V3 Kang Kai
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
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
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=4DF5D514.3030102@windriver.com \
--to=kai.kang@windriver.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