Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Tom Parkin <tom.parkin@pace.com>
To: openembedded-core@lists.openembedded.org
Subject: Using TCLIBC = "uclibc" in oe-core
Date: Tue, 21 Jun 2011 15:04:19 +0100	[thread overview]
Message-ID: <20110621140419.GA8589@raven.pace.internal> (raw)

[-- Attachment #1: Type: text/plain, Size: 1359 bytes --]

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".

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
-- 
Tom Parkin
Senior Software Engineer
Pace Plc

Bringing Technology Home

Victoria Road, Saltaire, West Yorkshire, BD18 3LF, United Kingdom. www.pace.com

Think before you print! Please consider the environment before printing this e-mail.


This message has been scanned for viruses by BlackSpider MailControl. - www.blackspider.com

[-- Attachment #2: 0001-Override-USE_NLS-for-glib-2.0-native-when-using-uCli.patch --]
[-- Type: text/plain, Size: 1136 bytes --]

From 7cab67af78f73408d7d86f7cfce78715cd32ae6b Mon Sep 17 00:00:00 2001
From: Tom Parkin <tom.parkin@pace.com>
Date: Tue, 21 Jun 2011 14:33:22 +0100
Subject: [PATCH] Override USE_NLS for glib-2.0-native when using uClibc

We don't use NLS for uClibc, but glib-2.0-native refuses to build
if USE_NLS is not "yes" (ref. meta/recipes-core/glib-2.0/glib-2.0.inc).

As a cunning work around, override USE_NLS for glib-2.0-native.  This
allows initial bitbake tasklist parsing and assembly to complete
successfully.
---
 meta/conf/distro/include/tclibc-uclibc.inc |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/meta/conf/distro/include/tclibc-uclibc.inc b/meta/conf/distro/include/tclibc-uclibc.inc
index c421f5e..408966b 100644
--- a/meta/conf/distro/include/tclibc-uclibc.inc
+++ b/meta/conf/distro/include/tclibc-uclibc.inc
@@ -14,7 +14,7 @@ PREFERRED_PROVIDER_virtual/libiconv ?= "libiconv"
 PREFERRED_PROVIDER_virtual/libintl ?= "gettext"
 
 USE_NLS ?= "no"
-USE_NLS_glib-2.0 = "yes"
+USE_NLS_pn-glib-2.0-native = "yes"
 
 CXXFLAGS += "-fvisibility-inlines-hidden"
 
-- 
1.7.4.4


             reply	other threads:[~2011-06-21 14:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-21 14:04 Tom Parkin [this message]
2011-06-21 14:50 ` Using TCLIBC = "uclibc" in oe-core Khem Raj
2011-06-21 14:53 ` Mark Hatle
2011-06-21 14:54 ` Phil Blundell
2011-06-21 15:02   ` Khem Raj
2011-06-21 16:49   ` Richard Purdie
2011-06-22 13:13     ` Tom Parkin

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=20110621140419.GA8589@raven.pace.internal \
    --to=tom.parkin@pace.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