From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 01/11] bitbake.conf: Add weak definition for USE_NLS
Date: Fri, 29 Jun 2012 12:43:13 +0100 [thread overview]
Message-ID: <1340970193.23146.148.camel@ted> (raw)
In-Reply-To: <638231d75b991a3be5c9aed5add4c56e66f79fe0.1340919157.git.raj.khem@gmail.com>
On Thu, 2012-06-28 at 14:36 -0700, Khem Raj wrote:
> USE_NLS is generally defined for uclibc based system builds
> and generally its defined to 'no' there. However this variable
> does not exist at all for eglibc/glibc distributions. This
> patch adds a weak definition to 'yes' on eglibc based system
> builds. This will ease out some of the cryptic contructs we
> have to define certain options based on USE_NLS and also
> checking got uclibc at the same time to avoid pythong exceptions
> when its not defined.
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> meta/conf/bitbake.conf | 1 +
> meta/conf/distro/include/tclibc-eglibc.inc | 2 ++
> 2 files changed, 3 insertions(+)
>
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index 9b26580..9377ee6 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -98,6 +98,7 @@ TUNE_ASARGS ??= ""
> TUNE_FEATURES ??= "${TUNE_FEATURES_tune-${DEFAULTTUNE}}"
> LIBCEXTENSION ??= ""
> ABIEXTENSION ??= ""
> +USE_NLS ??= "yes"
>
> TARGET_ARCH = "${TUNE_ARCH}"
> TARGET_OS = "linux${LIBCEXTENSION}${ABIEXTENSION}"
> diff --git a/meta/conf/distro/include/tclibc-eglibc.inc b/meta/conf/distro/include/tclibc-eglibc.inc
> index 4f5607f..e2ca4e8 100644
> --- a/meta/conf/distro/include/tclibc-eglibc.inc
> +++ b/meta/conf/distro/include/tclibc-eglibc.inc
> @@ -32,6 +32,8 @@ LIBC_LOCALE_DEPENDENCIES = "\
> eglibc-gconv-iso8859-1 \
> eglibc-gconv-iso8859-15"
>
> +USE_NLS ?= "yes"
> +
> def get_libc_locales_dependencies(d):
> if 'libc-locales' in (d.getVar('DISTRO_FEATURES', True) or '').split() :
> return d.getVar('LIBC_LOCALE_DEPENDENCIES', True) or ''
This second change is just pointless noise now :)
Cheers,
Richard
next prev parent reply other threads:[~2012-06-29 11:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 21:34 [PATCH 00/11] toolchain updates Khem Raj
2012-06-28 21:36 ` [PATCH 01/11] bitbake.conf: Add weak definition for USE_NLS Khem Raj
2012-06-29 11:43 ` Richard Purdie [this message]
2012-06-28 21:36 ` [PATCH 02/11] libgcc: Remove unpackage unwind.h Khem Raj
2012-06-28 21:36 ` [PATCH 03/11] gcc-configure-sdk, gcc-configure-cross: Dont recompute USE_NLS Khem Raj
2012-06-28 21:36 ` [PATCH 04/11] eglibc: support mipsel little endian, filter out -march=mips32 Khem Raj
2012-06-28 21:36 ` [PATCH 05/11] eglibc-2.15: Update to latest on 2.15 branch Khem Raj
2012-06-28 21:36 ` [PATCH 06/11] kconfig-frontends: New recipe Khem Raj
2012-06-28 21:36 ` [PATCH 07/11] uclibc: Separate the bits between uclibc and uclibc-initial Khem Raj
2012-06-28 21:36 ` [PATCH 08/11] uclibc-git: Update for building systemd Khem Raj
2012-06-28 21:36 ` [PATCH 09/11] uclibc-0.9.33: add posix_fallocate implementation Khem Raj
2012-06-28 21:36 ` [PATCH 10/11] bison: link in librt on uclibc Khem Raj
2012-06-28 21:36 ` [PATCH 11/11] glib-2.0: Add missing dependency on virtual/libiconv Khem Raj
2012-06-29 12:34 ` [PATCH 00/11] toolchain updates Richard Purdie
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=1340970193.23146.148.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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