Re: Using TCLIBC = "uclibc" in oe-core

[Mark Hatle <mark.hatle@windriver.com>]

On 6/21/11 9:04 AM, Tom Parkin wrote:
> Hi list,
> 
> I'm trying to set up a working openembedded-core/uClibc mipsel
> environment.  I found that setting TCLIBC = "uclibc" in local.conf
> yielded the following:
> 
> ERROR: Nothing PROVIDES 'glib-2.0-native'
> 
> I traced this down to code in meta/recipes-core/glib-2.0/glib-2.0.inc,
> which raises a SkipPackage exception if USE_NLS = "no".

Sounds like this should behave differently for the glib-2.0-native and glib-2.0
target.  I don't know how to detect the package type in python code though,
someone else might know.

--Mark

> The reason that USE_NLS = "no" in this case is that
> meta/conf/distro/include/tclibc-uclibc.inc sets USE_NLS ?= "no".
> 
> Looking further at tclibc-uclibc.inc, though, it appears that there is
> some code attempting to work around this issue:
> 
> USE_NLS_glib-2.0 = "yes"
> 
> Sadly, this appears to get ignored.  Following this up on the #yocto
> IRC channel, it seems that a more appropriate formulation of the above
> would be:
> 
> USE_NLS_pn-glib-2.0-native = "yes"
> 
> The attached patch allows me to (at least) assemble the bitbake task
> list when TCLIBC = "uclibc".  I'm not sure whether this is the correct
> approach, though.
> 
> Any comments?
> 
> Many thanks,
> Tom
> 
> 
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core