On 2011年06月13日 17:27, Phil Blundell wrote:
On Mon, 2011-06-13 at 17:15 +0800, Kang Kai wrote:
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.
I'm not quite sure I understood what you wrote above. But I think what
I was asking was, why doesn't eglibc just look at the existing ipv6
DISTRO_FEATURE?
It seems DISTRO_FEATURE doesn't want to enable ipv6 by default, but
eglibc needs supports it.
p.
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
